We're gonna need non-dir syscall callbacks, which will make dir_ops a
misnomer. Let's rename kernfs_dir_ops to kernfs_syscall_ops.
This is pure rename.
Signed-off-by: Tejun Heo
---
fs/kernfs/dir.c| 25 +
include/linux/kernfs.h | 18 +-
2 files
On 02/03/2014 12:55 PM, Borislav Petkov wrote:
On Thu, Jan 30, 2014 at 08:54:13PM +0100, Borislav Petkov wrote:
Yeah, it is simpler. Ok, will change.
Ok, let's have another run at it. This one takes care of the relocated
ramdisk on 64-bit too, as we do it there also, not only on 32-bit. It
On 1/21/2014 3:03 PM, Aravind Gopalakrishnan wrote:
The current logic that returns (sys_addr >> 8) & 0x7 when
num_dcts_intlv = 4 is incorrect. We should really be doing-
If intlv_addr = 0x4, then interleave on bits [9:8] and if
intlv_addr = 0x5, interleave on bits [10:9].
Refer F15 M30h BKDG
On 18/01/14 20:33, Marek Vasut wrote:
On Saturday, January 18, 2014 at 08:05:18 PM, Alexandre Belloni wrote:
Checking the channel number is useless since mxs_lradc_read_raw() is called
from a controlled environment and the driver is responsible for filing the
struct iio_chan_spec.
As sysfs was kernfs's only user, kernfs has been piggybacking on
CONFIG_SYSFS; however, kernfs is scheduled to grow a new user very
soon. Introduce a separate config option CONFIG_KERNFS which is to be
selected by kernfs users.
Signed-off-by: Tejun Heo
Cc: linux-fsde...@vger.kernel.org
---
kernfs_deactivate() forgot to check whether KERNFS_LOCKDEP is set
before performing lockdep annotations and ends up feeding
uninitialized lockdep_map to lockdep triggering warning like the
following on USB stick hotunplug.
usb 1-2: USB disconnect, device number 2
INFO: trying to register
This toggles TIF_SYSCALL_AUDIT as needed when rules change instead of
leaving it set whenever rules might be set in the future. This reduces
syscall latency from >60ns to closer to 40ns on my laptop.
Cc: Oleg Nesterov
Cc: Steve Grubb
Cc: Eric Paris
Signed-off-by: Andy Lutomirski
---
This
kernfs_iop_lookup(), kernfs_dir_pos() and kernfs_dir_next_pos() were
missing kernfs_active() tests before using the found kernfs_node. As
deactivated state is currently visible only while a node is being
removed, this doesn't pose an actual problem. e.g. lookup succeeding
on a deactivated node
A write to a kernfs_node is buffered through a kernel buffer. Writes
<= PAGE_SIZE are performed atomically, while larger ones are executed
in PAGE_SIZE chunks. While this is enough for sysfs, cgroup which is
scheduled to be converted to use kernfs needs a bit more control over
it.
This patch
Implement helpers to determine node from dentry and root from
super_block. Also add a kernfs_rename_ns() wrapper which assumes NULL
namespace. These generally make sense and will be used by cgroup.
v2: Some dummy implementations for !CONFIG_SYSFS was missing. Fixed.
Reported by kbuild test
kernfs_node->parent and ->name are currently marked as "published"
indicating that kernfs users may access them directly; however, those
fields may get updated by kernfs_rename[_ns]() and unrestricted access
may lead to erroneous values or oops.
Protect ->parent and ->name updates with a irq-safe
Add a private data field to be used by kernfs file operations. This
generally makes sense and will be used by cgroup.
Signed-off-by: Tejun Heo
---
include/linux/kernfs.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/kernfs.h b/include/linux/kernfs.h
index 47f5235..9ca0f09
Hello,
This patchset makes various updates in preparation of cgroup's kernfs
conversion. Changes from the last take[L] are
* Refreshed on top of v3.14-rc1.
* 0010-kernfs-add-CONFIG_KERNFS.patch added.
This patchset contains the following 10 patches.
On Mon, Feb 3, 2014 at 10:26 AM, David Herrmann wrote:
> Hi
>
> On Sun, Feb 2, 2014 at 5:50 AM, Benjamin Tissoires
> wrote:
>> It was missing, so adding it.
>>
>> Signed-off-by: Benjamin Tissoires
>> ---
>> drivers/hid/uhid.c | 17 +
>> 1 file changed, 17 insertions(+)
>>
>>
This toggles TIF_SYSCALL_AUDIT as needed when rules change instead of
leaving it set whenever rules might be set in the future. This reduces
syscall latency from >60ns to closer to 40ns on my laptop.
Cc: Oleg Nesterov
Cc: Steve Grubb
Cc: Eric Paris
Signed-off-by: Andy Lutomirski
---
Changes
Hi Arnd,
First of all, thanks for reviewing this!
On Mon, Feb 03, 2014 at 06:46:10PM +, Arnd Bergmann wrote:
> On Monday 03 February 2014 18:33:48 Liviu Dudau wrote:
> > +/**
> > + * pci_host_bridge_of_get_ranges - Parse PCI host bridge resources from DT
> > + * @dev: device node of the host
kernfs_addrm_cxt and the accompanying kernfs_addrm_start/finish() were
added because there were operations which should be performed outside
kernfs_mutex after adding and removing kernfs_nodes. The necessary
operations were recorded in kernfs_addrm_cxt and performed by
kernfs_addrm_finish();
kernfs_unmap_bin_file() is supposed to unmap all memory mappings of
the target file before kernfs_remove() finishes; however, it currently
is being called from kernfs_addrm_finish() and has the same race
problem as the original implementation of deactivation when there are
multiple removers - only
There currently are two mechanisms gating active ref lockdep
annotations - KERNFS_LOCKDEP flag and KERNFS_ACTIVE_REF type mask.
The former disables lockdep annotations in kernfs_get/put_active()
while the latter disables all of kernfs_deactivate().
While KERNFS_ACTIVE_REF also behaves as an
The recursive nature of kernfs_remove() means that, even if
kernfs_remove() is not allowed to be called multiple times on the same
node, there may be race conditions between removal of parent and its
descendants. While we can claim that kernfs_remove() shouldn't be
called on one of the
kernfs_node->u.completion is used to notify deactivation completion
from kernfs_put_active() to kernfs_deactivate(). We now allow
multiple racing removals of the same node and the current removal
scheme is no longer correct - kernfs_remove() invocation may return
before the node is properly
Sometimes it's necessary to implement a node which wants to delete
nodes including itself. This isn't straightforward because of kernfs
active reference. While a file operation is in progress, an active
reference is held and kernfs_remove() waits for all such references to
drain before
driver-core now supports synchrnous self-deletion of attributes and
the asynchrnous removal mechanism is scheduled for removal. Use it
instead of device_schedule_callback(). This makes "delete" behave
synchronously.
Signed-off-by: Tejun Heo
Cc: "James E.J. Bottomley"
Cc:
driver-core now supports synchrnous self-deletion of attributes and
the asynchrnous removal mechanism is scheduled for removal. Use it
instead of device_schedule_callback().
* Conversions in arch/s390/pci/pci_sysfs.c and
drivers/s390/block/dcssblk.c are straightforward.
*
KERNFS_REMOVED is used to mark half-initialized and dying nodes so
that they don't show up in lookups and deny adding new nodes under or
renaming it; however, its role overlaps that of deactivation.
It's necessary to deny addition of new children while removal is in
progress; however, this role
driver-core now supports synchrnous self-deletion of attributes and
the asynchrnous removal mechanism is scheduled for removal. Use it
instead of device_schedule_callback(). This makes "remove" behave
synchronously.
Signed-off-by: Tejun Heo
Cc: Bjorn Helgaas
Cc: linux-...@vger.kernel.org
---
Hello,
(Please note that 0001 was posted separately before and should be
routed through driver-core-linus)
This is v5 of kernfs self-removal patchset. The changes from v4[4]
are
* Being rebased on v3.14-rc1.
* 0001-kernfs-make-kernfs_deactivate-honor-KERNFS_LOCKDEP-f.patch
separated out
All device_schedule_callback_owner() users are converted to use
device_remove_file_self(). Remove now unused
{sysfs|device}_schedule_callback_owner().
Signed-off-by: Tejun Heo
---
drivers/base/core.c| 33 --
fs/sysfs/file.c| 92
On Mon, Feb 3, 2014 at 11:04 AM, David Herrmann wrote:
> Hi
>
> On Sun, Feb 2, 2014 at 5:50 AM, Benjamin Tissoires
> wrote:
>> Add output_report and raw_request to i2c-hid.
>> Hopefully, we will manage to have the same transport level between
>> all the transport drivers.
>>
>> Signed-off-by:
> On Fri, Jan 31, 2014 at 09:46:51PM +, Andrew Chew wrote:
> > This optional property can be used to specify which timers are to be
> > used for hardware watchdog timeouts (via a tegra wdt driver).
>
> Is there any reason that a particular timer should be used?
I worry about colliding with
On Monday 03 February 2014 18:43:48 Liviu Dudau wrote:
> diff --git a/arch/arm64/include/asm/io.h b/arch/arm64/include/asm/io.h
> index 4cc813e..ce5bad2 100644
> --- a/arch/arm64/include/asm/io.h
> +++ b/arch/arm64/include/asm/io.h
> @@ -120,9 +120,13 @@ static inline u64 __raw_readq(const
> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: Monday, February 03, 2014 8:40 AM
> To: Andrew Chew; t...@linutronix.de; swar...@wwwdotorg.org;
> thierry.red...@gmail.com; abres...@chromium.org; dgr...@chromium.org;
> kati...@chromium.org
> Cc: linux-kernel@vger.kernel.org;
On Mon, Feb 3, 2014 at 6:34 PM, Ian Pilcher wrote:
> Shouldn't size_t use %zu?
Technically yes. %zi/%zd prints signed numbers (ssize_t), while %zu prints
unsigned (size_t).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
On Mon, 3 February 2014 11:37:29 -0500, Theodore Ts'o wrote:
>
> So we could take the struct pt_regs which we get from get_irq_regs(),
> XOR them together and use them to feed into input[2] amd input[3] in
> add_interrupt_randomness(). Or some other way of distributing the
> values of all of the
On Monday 03 February 2014 18:33:48 Liviu Dudau wrote:
> +/**
> + * pci_host_bridge_of_get_ranges - Parse PCI host bridge resources from DT
> + * @dev: device node of the host bridge having the range property
> + * @resources: list where the range of resources will be added after DT
> parsing
> +
Hi,
This patch adds support for PCI to AArch64. It is based on the patch posted
here [1] that adds support for creating generic host bridge structure from
device tree. With that in place, I was able to boot an FPGA platform that
has PCIe host bridge support and use a PCIe network card.
The API
Use the generic host bridge functions to provide support for
PCI Express on arm64. There is no support for ISA memory.
Signed-off-by: Liviu Dudau
---
arch/arm64/Kconfig| 17 +++
arch/arm64/include/asm/Kbuild | 1 +
arch/arm64/include/asm/io.h | 4 ++
On Sun, 2014-02-02 at 22:12 +0100, Peter Zijlstra wrote:
> The way I wrote that same loop in step-B, is:
>
>
> for (;;) {
> if (*lock == node && cmpxchg(lock, node, prev) == node)
> return
>
> next = xchg(>next, NULL); /* B -> A */
>
On Mon, 2014-02-03 at 11:04 -0500, Alan Stern wrote:
> On Mon, 3 Feb 2014, Paul Bolle wrote:
> > This message cab still be seen when booting v3.14-rc1. Is a patch to
> > downgrade this message to dev_dbg() - from Josh, Felipe or someone else
> > - queued somewhere?
>
>
On Mon, Feb 03, 2014 at 03:58:06PM +0100, Jan Kara wrote:
> On Fri 31-01-14 11:49:01, Johannes Weiner wrote:
> > On Wed, Jan 29, 2014 at 02:11:02PM +0900, Minchan Kim wrote:
> > > >The only way to make these semantics clean is either
> > > >
> > > > a) have vrange() return a range ID so
Hi,
On Wed, Dec 04, 2013 at 03:29:53PM -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 03, 2013 at 11:46:50AM -0800, David Daney wrote:
> > From: David Daney
> >
> > Tested against both EdgeRouter LITE (no bootloader supplied device
> > tree), and ebb5610 (device tree supplied by bootloader).
>
Several platforms use a rather generic version of parsing
the device tree to find the host bridge ranges. Move that
into the generic PCI code and use it to create a pci_host_bridge
structure that can be used by arch code.
Based on early attempts by Andrew Murray to unify the code.
Used powerpc
Following the discussion started here [1], I now have a proposal for tackling
generic support for host bridges described via device tree. It is an initial
stab at it, to try to get feedback and suggestions, but it is functional enough
that I have PCI Express for arm64 working on an FPGA using the
On Mon, Feb 3, 2014 at 10:11 AM, Oleg Nesterov wrote:
> On 02/03, Andy Lutomirski wrote:
>>
>> @@ -911,6 +918,47 @@ static inline struct audit_context
>> *audit_alloc_context(enum audit_state state)
>> return context;
>> }
>>
>> +void audit_inc_n_rules()
>> +{
>> + struct task_struct
From: Colin Cross
Move the userspace interface of ashmem.h to
drivers/staging/android/uapi/ashmem.h
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Colin Cross
[jstultz: Minor commit message tweak]
Signed-off-by: John Stultz
---
drivers/staging/android/ashmem.h |
From: Borislav Petkov
Hold down when it makes sense to enable CONFIG_DEBUG_INFO and when
CONFIG_KALLSYMS suffices.
Signed-off-by: Borislav Petkov
Link:
http://lkml.kernel.org/r/CA%2B55aFw_xs1tUteDrXz21QZB7BFk5p%2BF5NZ-SpV=cuvjefw...@mail.gmail.com
Cc: Andrew Morton
Cc: Linus Torvalds
---
Hi Will, Arnaldo,
On 24 January 2014 17:35, Will Deacon wrote:
> Hi Jean,
>
> On Wed, Jan 22, 2014 at 02:11:15PM +, Jean Pihet wrote:
>> Add AARCH64 specific support. This includes the following:
>> - AARCH64 perf registers definition and hooks,
>> - compat mode registers use, i.e. profiling
From: Colin Cross
Move the userspace interface of binder.h to
drivers/staging/android/uapi/binder.h.
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Colin Cross
[jstultz: Worked out the collisions from some of the type changes
made upstream. Also minor commit subject
From: Greg Hackmann
Add stubs for kernels without CONFIG_SW_SYNC
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Greg Hackmann
[jstultz: resolved minor conflict, tweaked commit message]
Signed-off-by: John Stultz
---
drivers/staging/android/sw_sync.h | 17
From: Colin Cross
Move the userspace interface of android_alarm.h to
drivers/staging/android/uapi/android_alarm.h
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Colin Cross
[jstultz: minor commit msg tweak]
Signed-off-by: John Stultz
---
I recently went through the AOSP common.git android/3.10 tree to
try to pull fixes that haven't been submitted upstream. I've
cherry picked those patches and wanted to submit them here for
review, and for hopeful inclusion into staging for 3.15.
In most cases the patches cherry-picked right over.
On Sat, Feb 01, 2014 at 04:23:59PM -0800, Guenter Roeck wrote:
As previously mentioned please fix your mailer to word wrap at a
sensible limit.
> Seems to me it would be useful to have it, but then devm_clk_enable()
> doesn't exist either, so I wonder if there is a reason for not having
> it.
From: Colin Cross
Move the userspace interfaces of sync.h and sw_sync.h to
drivers/staging/android/uapi/
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Colin Cross
[jstultz: Fixed up some conflicts from upstream spelling fixes]
Signed-off-by: John Stultz
---
On Sun, Feb 2, 2014 at 10:56 PM, Suresh Siddha wrote:
>
> Other patch which cleans up the irq_enable/disable logic in
> math_state_restore() has been sent yesterday. You can run your
> experiments with both these patches if you want. But your issue should
> get fixed with just the appended patch
From: Mitchel Humpherys
It can be slightly annoying to figure out which files under the ion
debugfs directory are heap debug files and which ones are client debug
files. Create separate subdirectories under ion to hold the different
types of debug files.
Cc: Greg KH
Cc: Colin Cross
Cc:
From: Mitchel Humpherys
Currently, we copy the pointer passed in to ion_client_create without
making a copy of the string itself. This approach is problematic since
it relies on the client keeping the name string in working order.
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
From: Prakash Kamliya
There is a race condition
Assume we have *one* sync_fence object, with *one* sync_pt
which belongs to *one* sync_timeline, given this condition,
sync_timeline->kref will have two counts, one for sync_timeline
(implicit) and another for sync_pt.
Assume following is the
From: Alistair Strachan
Before this change, a timeline would only be removed from the timeline
list *after* the sync driver had its release_obj() called. However, the
driver's release_obj() may free resources needed by print_obj().
Although the timeline list is locked when print_obj() is
From: Todd Poynor
Avoid holding ashmem_mutex across code that can page fault. Page faults
grab the mmap_sem for the process, which are also held by mmap calls
prior to calling ashmem_mmap, which locks ashmem_mutex. The reversed
order of locking between the two can deadlock.
The calls that can
Add AARCH64 specific support. This includes the following:
- AARCH64 perf registers definition and hooks,
- compat mode registers use, i.e. profiling a 32-bit binary on
a 64-bit system,
- unwinding using the dwarf information from the .debug_frame
section of the ELF binary,
- unwinding using
This patch implements the functions required for the perf registers API,
allowing the perf tool to interface kernel register dumps with libunwind
in order to provide userspace backtracing.
Compat mode is also supported.
Only the general purpose user space registers are exported, i.e.:
From: Mitchel Humpherys
Currently, if multiple Ion clients are created with the same name, only
the first one shows up in debugfs. Rectify this by adding a
monotonically-increasing serial number to the debug names of Ion
clients.
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
When profiling a 32-bit application, user space callchain unwinding
using the frame pointer is performed in compat mode. The code is taken
over from the AARCH32 code and adapted to work on AARCH64.
Signed-off-by: Jean Pihet
Acked-by: Will Deacon
---
arch/arm64/kernel/perf_event.c | 75
From: Colin Cross
Fix a few bugs in ion_system_heap:
Initialize the list node in the info block.
Don't store size_remaining in a signed long, allocating >2GB
could overflow, resulting in a call to sg_alloc_table with
nents=0 which panics. alloc_largest_available will never
return a block
Add support for unwinding using the dwarf information in compat
mode. Using the correct user stack pointer allows perf to record
the frames correctly in the native and compat modes.
Note that although the dwarf frame unwinding works ok using
libunwind in native mode (on ARMv7 & ARMv8), some
From: Laura Abbott
Currently, Ion registers all debugfs entries for clients
via pid. If there are multiple kernel clients, this means
the debugfs entry only gets created for the first one. Fix
this by creating debugfs entries by name always. When
creating user clients, specify the name via the
From: Colin Cross
Every heap that uses deferred frees is going to need a shrinker
to shrink the freelist under memory pressure. Rather than
requiring each heap to implement a shrinker, automatically
register a shrinker if the deferred free flag is set.
The system heap also needs to shrink its
From: Mitchel Humpherys
Currently, when we free a buffer it might actually just go back into a
heap-specific page pool rather than going back to the system. This poses
a problem because sometimes (like when we're running a shrinker in low
memory conditions) we need to force the memory associated
This patch hooks in the perf_regs and libunwind code for ARM64.
The tools/perf/arch/arm64 is created; it contains the arch specific
code for DWARF unwinding.
Signed-off-by: Jean Pihet
Acked-by: Will Deacon
---
tools/perf/arch/arm64/Makefile| 7 +++
On Mon 03 Feb 2014 12:54:05 PM EST, David Sterba wrote:
On Thu, Jan 30, 2014 at 04:52:54PM -0500, Chris Mason wrote:
Chris Mason (3) commits (+64/-32):
Btrfs: setup inode location during btrfs_init_inode_locked (+9/-9)
Btrfs: don't use ram_bytes for uncompressed inline items (+52/-22)
From: Laura Abbott
The compat ioctl for ION_IOC_FREE currently passes allocation data
instead of the free data. Correct this.
Cc: Greg KH
Cc: Colin Cross
Cc: Android Kernel Team
Signed-off-by: Laura Abbott
[jstultz: Folded in a small build fix]
Signed-off-by: John Stultz
---
On Mon, Feb 03, 2014 at 04:57:18PM +, Will Deacon wrote:
> > mov[tw]: why?
> > Then we end up battling different available immediate fields in A32/T32
> > instruction sets and v5/v6/v7 architecture versions.
>
> I was making the assumption that UEFI was going to be v7 only... is this not
>
On 02/03, Andy Lutomirski wrote:
>
> @@ -911,6 +918,47 @@ static inline struct audit_context
> *audit_alloc_context(enum audit_state state)
> return context;
> }
>
> +void audit_inc_n_rules()
> +{
> + struct task_struct *p, *g;
> +
> + write_lock(_rules_lock);
> +
> + if
On Thu, Jan 30, 2014 at 08:54:13PM +0100, Borislav Petkov wrote:
> Yeah, it is simpler. Ok, will change.
Ok, let's have another run at it. This one takes care of the relocated
ramdisk on 64-bit too, as we do it there also, not only on 32-bit. It
boots fine here on the 32/64-bit guests.
---
From:
On Thu, Jan 30, 2014 at 04:52:54PM -0500, Chris Mason wrote:
> Chris Mason (3) commits (+64/-32):
> Btrfs: setup inode location during btrfs_init_inode_locked (+9/-9)
> Btrfs: don't use ram_bytes for uncompressed inline items (+52/-22)
The patches are CC: stable, but haven't gone through
This toggles TIF_SYSCALL_AUDIT as needed when rules change instead of
leaving it set whenever rules might be set in the future. This reduces
syscall latency from >60ns to closer to 40ns on my laptop.
Cc: Oleg Nesterov
Cc: Steve Grubb
Cc: Eric Paris
Signed-off-by: Andy Lutomirski
---
This is
On 01/31, Alex Thorlton wrote:
>
> This patch adds a VM_INIT_DEF_MASK,
Perhaps it makes sense to tell a bit more... We add this mask to preserve
VM_NOHUGEPAGE after fork/exec. And this is obviously affects s390, say the
result of KVM_S390_ENABLE_SIE will be preserved.
I hope this is fine, but
setup-bus.o is now included unconditionally as of commit
7dc30303342562685392c8c7aa5194e98fd27625. Remove it from
the per-arch list of object files.
Signed-off-by: Liviu Dudau
---
drivers/pci/Makefile | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git
On Mon, Feb 03, 2014 at 08:46:07AM -0500, Christopher Covington wrote:
> Hi Christoffer,
>
> On 02/02/2014 11:56 PM, Christoffer Dall wrote:
> > On Thu, Jan 30, 2014 at 11:54:46AM -0500, Christopher Covington wrote:
> >> I think it would be informative to provide pointers here to commonly used
>
Maxime Ripard writes:
> Hi Kevin,
>
> On Thu, Jan 30, 2014 at 03:52:16PM -0800, Kevin Hilman wrote:
>> On Wed, Jan 29, 2014 at 5:32 AM, Maxime Ripard
>> wrote:
>> > On Wed, Jan 29, 2014 at 12:25:20PM +, Mark Brown wrote:
>> >> On Wed, Jan 29, 2014 at 12:10:48PM +0100, Maxime Ripard wrote:
On Sat, Feb 1, 2014 at 4:16 AM, Alexandre Courbot wrote:
> Finally, support for probing GK20A is added in the last 2 patches. It should
> be
> noted that contrary to what Nouveau currently expects, GK20A does not embed
> any
> display hardware (that part being handled by tegradrm). So this
Shouldn't size_t use %zu?
--
Ian Pilcher arequip...@gmail.com
Sent from the cloud -- where it's already tomorrow
On Mon, Feb 03, 2014 at 08:52:10AM -0800, Guenter Roeck wrote:
> On Mon, Feb 03, 2014 at 03:41:09PM +, Mark Brown wrote:
> > It's on a fixes tag so it'll go in next time I send stuff to Linus,
> > it'll go next time I send something to him. That's usually about once
> > per release.
On Fri, Jan 31, 2014 at 03:00:58PM -0800, Andrew Morton wrote:
> On Fri, 31 Jan 2014 12:23:45 -0600 Alex Thorlton wrote:
>
> > This patch adds a VM_INIT_DEF_MASK, to allow us to set the default flags
> > for VMs. It also adds a prctl control which alllows us to set the THP
> > disable bit in
On 02/02/2014 12:07 PM, Stefan Lippers-Hollmann wrote:
Hi
[ CC'ing the relevant parties ]
On Sunday 02 February 2014, Dave Jones wrote:
On Sun, Feb 02, 2014 at 03:41:27AM -0800, scan-ad...@coverity.com wrote:
>
> Please find the latest report on new defect(s) introduced to Linux found
On Fri, Jan 31, 2014 at 02:52:24PM -0800, Andrew Morton wrote:
> On Fri, 31 Jan 2014 12:23:43 -0600 Alex Thorlton wrote:
>
> > This reverts commit 8e72033f2a489b6c98c4e3c7cc281b1afd6cb85cm, and adds
>
> 'm' is not a hex digit ;)
My mistake! Sorry about that.
> > in code to fix up any issues
Hello Greg,
Would you care to comment on this patch?
It adds some Kconfig clutter, but this is removed again in the next patch
(http://marc.info/?l=linux-arm-kernel=139101443708663=2),
which has already been acked by hpa here:
http://marc.info/?l=linux-arm-kernel=139101589509168=2
Example
Hello JJ,
On 03/02/2014 17:46, Jean-Jacques Hiblot wrote:
The name provided to request_irq() must be valid until the irq is
released.
This patch allocates and formats the string with kasprintf().
Thanks for reporting this bug.
Signed-off-by: Jean-Jacques Hiblot
---
On 02/02/2014 07:16 PM, Stephen Rothwell wrote:
> Hi all,
>
> This tree fails (more than usual) the powerpc allyesconfig build.
>
> Changes since 20140131:
>
on i386:
when CONFIG_REGMAP_I2C=m:
sound/built-in.o: In function `snd_soc_codec_set_cache_io':
(.text+0x29555): undefined reference to
On Fri, Jan 31, 2014 at 09:46:51PM +, Andrew Chew wrote:
> This optional property can be used to specify which timers are to be used
> for hardware watchdog timeouts (via a tegra wdt driver).
Is there any reason that a particular timer should be used?
This shouldn't even mention the driver,
On Mon, Feb 03, 2014 at 04:57:56PM +, Pearson, Greg wrote:
[..]
> > So I will not be too worried about skipping seemingly corrupted ELf
> > notes. I think giving a warning makes sense though. Is somebody
> > overwriting the memory area in kenrel reserved for per cpu PT_NOTE.
>
> I haven't
Hi
On Mon, Feb 3, 2014 at 5:21 PM, Benjamin Tissoires
wrote:
> On Mon, Feb 3, 2014 at 11:06 AM, David Herrmann wrote:
>> Hi
>>
>> On Sun, Feb 2, 2014 at 5:50 AM, Benjamin Tissoires
>> wrote:
>>> hid-logitech-dj uses its own ->hidinput_input_event() instead of
>>> the generic binding in
On 01/31/2014 10:05 PM, Michael Ellerman wrote:
> I pointed some folks at this and they wondered why it wasn't in the
> kernel Documentation directory. So now it is.
>
> Signed-off-by: Daniel Vetter
> Signed-off-by: Michael Ellerman
> ---
> Documentation/ioctl/00-INDEX | 2 +
>
On Mon, Feb 03, 2014 at 03:48:29PM +0100, Jan Kara wrote:
> On Sat 01-02-14 17:48:27, Frederic Weisbecker wrote:
> > On Mon, Dec 23, 2013 at 09:39:22PM +0100, Jan Kara wrote:
> > > Block layer currently abuses rq->csd.list.next for storing fifo_time.
> > > That is a terrible hack and completely
On 29/01/14 09:52, Jan Beulich wrote:
On 28.01.14 at 18:43, Roger Pau Monne wrote:
>> --- a/drivers/block/xen-blkback/blkback.c
>> +++ b/drivers/block/xen-blkback/blkback.c
>> @@ -985,17 +985,31 @@ static void __end_block_io_op(struct pending_req
>> *pending_req, int error)
>> * the
On 02/03/2014 08:47 AM, Vivek Goyal wrote:
> On Sun, Feb 02, 2014 at 02:25:25PM -0800, Eric W. Biederman wrote:
>> Andrew Morton writes:
>>
>>> On Sat, 1 Feb 2014 01:07:29 + "Pearson, Greg"
>>> wrote:
>>>
As far as I know the only consequence of dropping a PT_NOTE entry is
that it
Hi Andrew,
Please queue this patchset for the next merge window.
Andreas's three patches will add a new ioctl which helps to mitigate
overheads of garbage collection of nilfs. The original cover letter
can be seen at:
[1] http://marc.info/?l=linux-nilfs=139081676816008
there the userland
On Mon, Feb 03, 2014 at 04:46:36PM +, Leif Lindholm wrote:
> On Mon, Feb 03, 2014 at 04:00:51PM +, Will Deacon wrote:
> > > > > With the two call sites in uefi_phys.S as:
> > > > >
> > > > > ldr r5, =(CR_M)
> > > > > update_sctlrr12, , r5
> > > > > and
> > > > >
From: Andreas Rohner
This patch introduces the nilfs_sufile_set_suinfo function, which
expects an array of nilfs_suinfo_update structures and updates the
segment usage information accordingly.
This is basically a helper function for the newly introduced
NILFS_IOCTL_SET_SUINFO ioctl.
From: Andreas Rohner
With this ioctl the segment usage entries in the SUFILE can be
updated from userspace.
This is useful, because it allows the userspace GC to modify and update
segment usage entries for specific segments, which enables it to avoid
unnecessary write operations.
If a segment
301 - 400 of 1358 matches
Mail list logo
