On Mon, Oct 20, 2014 at 10:46:14AM +0200, Boris Brezillon wrote:
> read_page_raw and write_page_raw method description is not clear enough.
> It clearly specifies that ECC correction should not be involved but does
> not talk about specific layout (by layout I mean where in-band and
> out-of-band
On 10/23/2014 12:55 PM, Andrew Lunn wrote:
[ ... ]
Does hwmon offer a function to sanitise a string?
No, that wasn't necessary so far. The 'name' string is a constant string
provided by the driver.
The switch index definitely should be used and i would probably
combine that with a sanitised
On 2014年10月24日 19:46, Haojian Zhuang wrote:
On Thu, Oct 23, 2014 at 10:04 PM, Zhou Wang wrote:
Signed-off-by: Zhou Wang
---
drivers/mtd/nand/Kconfig|5 +
drivers/mtd/nand/Makefile |1 +
drivers/mtd/nand/hisi504_nand.c | 836 +++
On Mon, 13 Oct 2014 13:35:04 -0400
Dave Jones wrote:
> Today in "rcu stall while fuzzing" news:
My bug report seems to be related with this topic:
Regression: kernel 3.17 halts sometimes (with Call trace)
https://bugzilla.kernel.org/show_bug.cgi?id=85941
Could somone take a
Quoting Aditya Kali (adityak...@google.com):
> >> +void free_cgroup_ns(struct cgroup_namespace *ns)
> >> +{
> >> + cgroup_put(ns->root_cgrp);
> >> + put_user_ns(ns->user_ns);
> >
> > This is a problem on error patch in copy_cgroup_ns. The
> > alloc_cgroup_ns() doesn't initialize these
On 10/24/2014 05:22 PM, Andy Lutomirski wrote:
> Is there any good reason not to use vmalloc for x86_64 stacks?
Additional TLB pressure if anything else.
Now, on the flipside: what is the *benefit*?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
test
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Fri, Oct 24, 2014 at 05:20:48PM -0700, Jay Vosburgh wrote:
> Paul E. McKenney wrote:
>
> >On Fri, Oct 24, 2014 at 03:59:31PM -0700, Paul E. McKenney wrote:
> [...]
> >> Hmmm... It sure looks like we have some callbacks stuck here. I clearly
> >> need to take a hard look at the sleep/wakeup
Kernel dump (WARN_ON) ocurred during system boot-up inside regmap_write():
[ cut here ]
WARNING: CPU: 0 PID: 47 at kernel/locking/lockdep.c:2744
lockdep_trace_alloc+0xe8/0x108()
DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
Modules linked in:
CPU: 0 PID: 47 Comm:
On Fri, Oct 24, 2014 at 10:14:12AM -0500, Felipe Balbi wrote:
> Hi Greg,
>
> Here's our first set of fixes for v3.18-rc cycle.
>
> Quite a few goodies here but the most important is that most gadget drivers
> (except for g_hid, g_midi and g_webcam) pass USB[23]0CV with MUSB and DWC3.
>
> All
> "Michael" == Michael L Semon writes:
Michael> There was nothing regarding integrity in /sys/block/sda. I was
Michael> under the impression that both bio integrity and T10 checksums
Michael> require hardware support from good hardware, so the config
Michael> items have always been shut
Hi all,
For arm32 platform. I want to know whether or not a mechanism in kernel can
snapshot tasks and cpus
information as the follow. If not, such a mechanism can be accepted by kernel.
...
TASK: [pid 1], [tgid 1], [linuxrc] [state S] [policy 0] [cpu 3]
EIP address: [<401945a4>]
This patch fixes the following sparse warnings:
drivers/staging/lustre/lnet/lnet/module.c:47:1: warning: symbol
'lnet_configure' was not declared. Should it be static?
drivers/staging/lustre/lnet/lnet/module.c:67:1: warning: symbol
'lnet_unconfigure' was not declared. Should it be static?
Apply __init marker to module's init function and __exit to module's
exit function as they both have no other usage.
Signed-off-by: Mariusz Gorski
---
drivers/staging/lustre/lnet/lnet/module.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
These patches fix some sparse warnings and apply __init and __exit
markers to module's init and exit functions.
v2: Add missing commit sign-offs
Mariusz Gorski (2):
staging: lustre: Reduce function visibility
staging: lustre: Use __init and __exit markers for lifecycle functions
Apply __init marker to module's init function and __exit to module's
exit function as they both have no other usage.
---
drivers/staging/lustre/lnet/lnet/module.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lnet/lnet/module.c
This patch fixes the following sparse warnings:
drivers/staging/lustre/lnet/lnet/module.c:47:1: warning: symbol
'lnet_configure' was not declared. Should it be static?
drivers/staging/lustre/lnet/lnet/module.c:67:1: warning: symbol
'lnet_unconfigure' was not declared. Should it be static?
These patches fix some sparse warnings and apply __init and __exit
markers to module's init and exit functions.
Mariusz Gorski (2):
staging: lustre: Reduce function visibility
staging: lustre: Use __init and __exit markers for lifecycle functions
drivers/staging/lustre/lnet/lnet/module.c |
On 10/24/2014 06:22 PM, H. Peter Anvin wrote:
>> By the principle of least surprise, I would expect "__u32 >> N", where
>> > N >= 32 to return zero instead of random garbage. For N < 32 it will
>> > return progressively smaller numbers, until it has shifted away all of
>> > the set bits, at which
Em Wed, Oct 22, 2014 at 10:36:00AM +0900, Namhyung Kim escreveu:
> Hi Jiri,
>
> On Thu, 16 Oct 2014 16:07:00 +0200, Jiri Olsa wrote:
> > hi,
> > adding some branch_info checks to prevent segfaults
> > on data without branch info.
> >
> > v2: using cmp_null as suggested by Namhyung
>
> For the
On 10/24/14 15:54, Martin K. Petersen wrote:
"Michael" == Michael L Semon writes:
Michael> This week, a simple `dc3dd wipe=/dev/sda5` operation had speeds
Michael> cut from 10-15 MB/s down to less than 1.8 MB/s. With this
Michael> method, syncs took so long that magic SysRq keys were needed
Is there any good reason not to use vmalloc for x86_64 stacks?
The tricky bits I've thought of are:
- On any context switch, we probably need to probe the new stack
before switching to it. That way, if it's going to fault due to an
out-of-sync pgd, we still have a stack available to handle the
Paul E. McKenney wrote:
>On Fri, Oct 24, 2014 at 03:59:31PM -0700, Paul E. McKenney wrote:
[...]
>> Hmmm... It sure looks like we have some callbacks stuck here. I clearly
>> need to take a hard look at the sleep/wakeup code.
>>
>> Thank you for running this!!!
>
>Could you please try the
ERROR: that open brace { should be on the previous line
Signed-off-by: Paul McQuade
---
drivers/staging/rtl8723au/core/rtw_ap.c | 130 ++--
1 file changed, 40 insertions(+), 90 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
On Fri, Oct 24, 2014 at 1:19 PM, H. Peter Anvin wrote:
> On 10/23/2014 12:38 PM, Eric Paris wrote:
>>>
>>> After the call __audit_syscall_entry aren't they already polluted?
>>> Isn't that the reason we need to reload EAX?
>>
>> Well, I guess EAX is special...
>>
>
> Because system calls are
ESAI may need to use fixed slot width to comply with external
CODEC. So this set_tdm_slot() call will allow the ESAI driver
to override its default dynamic slot width policy.
Signed-off-by: Nicolin Chen
---
sound/soc/fsl/fsl-asoc-card.c | 12
1 file changed, 12 insertions(+)
diff
When cpu-dai is the DAI Master (CBM_CFx), it may need some configurations,
set_sysclk() call for eample, for cpu-dai side in the hw_params(), even if
the set_bias_level() has already taken care of the codec-dai side.
So this patch just simply adds an additional condition.
Signed-off-by: Nicolin
The driver previously used 32-bit fixed slot width as default.
In result, ESAI might use 32-bit length to capture 16-bit width
audio slot from CODEC side when ESAI is running as DAI slave.
So this patch just removes the default slot_width so as to use
dynamic slot width. If there comes a specific
This series of patches add the support of dynamic slot width for
ESAI driver. To do this, the PATCH-1 removes the fixed width. In
order not to break those platforms that use fixed width, there
comes the PATCH-2 to apply an override of slot_width.
@Shengjiu,
Will you be available to test this
Hello!
Just a follow-up on the spirited LKML thread last February
(http://lwn.net/Articles/586838/, https://lwn.net/Articles/588300/).
Although we don't yet have anything resembling full solution, there has
been some good progress, which is documented in SC22/WG21 document N4215.
The official
Hi Frank,
On Thu, Oct 23, 2014 at 04:04:37PM +0200, Frank Blaschka wrote:
> > A domain is basically an abstraction for a DMA page table (or a
> > dma_table, as you call it on s390). So you can easily create similar
> > mappings for more than one device with it.
> >
> the clp instructions reports
ERROR: that open brace { should be on the previous line
Signed-off-by: Paul McQuade
---
drivers/staging/rtl8723au/core/rtw_ap.c | 137 ++--
1 file changed, 43 insertions(+), 94 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
Hi,
On Fri, Oct 24, 2014 at 4:07 PM, kbuild test robot
wrote:
>net/wireless/core.c: In function 'wiphy_new_nm':
>>> net/wireless/core.c:374:3: error: format not a string literal and no format
>>> arguments [-Werror=format-security]
> rv = dev_set_name(>wiphy.dev, requested_name);
>
On Fri, Oct 24, 2014 at 10:59 AM, Marc Zyngier wrote:
> Hi Bjorn,
>
> On 24/10/14 18:31, Bjorn Andersson wrote:
>> On Tue, Oct 21, 2014 at 2:34 AM, Marc Zyngier wrote:
[..]
>> I would prefer to see that you had explicit functions for the various things
>> that you would like to set and get. It
On Fri, Oct 24, 2014 at 03:59:31PM -0700, Paul E. McKenney wrote:
> On Fri, Oct 24, 2014 at 03:34:07PM -0700, Jay Vosburgh wrote:
> > Paul E. McKenney wrote:
> >
> > >On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
> > >> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
> > >> >
On Fri, Oct 24, 2014 at 03:34:07PM -0700, Jay Vosburgh wrote:
> Paul E. McKenney wrote:
>
> >On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
> >> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
> >> > On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
> >> > > On
Signed-off-by: Andy Lutomirski
---
include/linux/perf_event.h | 7 +++
kernel/events/core.c | 9 +
2 files changed, 16 insertions(+)
diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
index 893a0d07986f..c93aff25a459 100644
--- a/include/linux/perf_event.h
CR4 manipulation was split, seemingly at random, between direct
(write_cr4) and using a helper (set/clear_in_cr4). Unfortunately,
the set_in_cr4 and clear_in_cr4 helpers also poke at the boot code,
which only a small subset of users actually wanted.
This patch replaces all cr4 access in
From: Peter Zijlstra
Andy reported that the current state of event_idx is rather confused.
So remove all but the x86_pmu implementation and change the default to
return 0 (the safe option).
Reported-by: Andy Lutomirski
Signed-off-by: Peter Zijlstra (Intel)
---
arch/powerpc/perf/hv-24x7.c
The code is correct, but only for a rather subtle reason. This
confused me for quite a while when I read switch_mm, so clarify the
code to avoid confusing other people, too.
TBH, I wouldn't be surprised if this code was only correct by
accident.
Signed-off-by: Andy Lutomirski
---
Context switches and TLB flushes can change individual bits of CR4.
CR4 reads take several cycles, so store a shadow copy of CR4 in a
per-cpu variable.
To avoid wasting a cache line, I added the CR4 shadow to
cpu_tlbstate, which is already touched in switch_mm. The heaviest
users of the cr4
We currently allow any process to use rdpmc. This significantly
weakens the protection offered by PR_TSC_DISABLED, and it could be
helpful to users attempting to exploit timing attacks.
Since we can't enable access to individual counters, use a very
coarse heuristic to limit access to rdpmc:
While perfmon2 is a sufficiently evil library (it pokes MSRs
directly) that breaking it is fair game, it's still useful, so we
might as well try to support it. This allows users to write 2 to
/sys/devices/cpu/rdpmc to disable all rdpmc protection so that hack
like perfmon2 can continue to work.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/perf_event.c | 3 ++-
kernel/events/core.c | 5 +++--
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event.c b/arch/x86/kernel/cpu/perf_event.c
index 2176647fdbb7..00fbab7aa587 100644
---
This little series tightens up rdpmc permissions. With it applied,
rdpmc can only be used if a perf_event is actually mmapped. For now,
this is only really useful for seccomp.
At some point this could be further tightened up to only allow rdpmc
if an actual self-monitoring perf event that is
On Fri, Oct 24, 2014 at 03:06:13PM -0700, Davidlohr Bueso wrote:
> diff --git a/mm/fremap.c b/mm/fremap.c
> index 72b8fa3..11ef7ec 100644
> --- a/mm/fremap.c
> +++ b/mm/fremap.c
> @@ -238,13 +238,13 @@ get_write_lock:
> }
> goto out_freed;
>
Hello Maintainers:
Please help check this patch, when you have time.
Thanks.
On 10/4/14 21:11, Chen Gang wrote:
> syscall() is implemented in libc.so/a (e.g. for glibc, in "syscall.o"),
> so for normal ".o" files, it is undefined, neither can be found within
> kernel wide, so will break
On 10/16/14 5:03, Konrad Rzeszutek Wilk wrote:
> On Wed, Oct 15, 2014 at 08:20:06AM +0800, Chen Gang wrote:
>>
>> At least for me, what you said sound OK.
>
> Let me review it - next week.
Please help check this patch, when you have time.
Thanks.
>>
>> Thanks.
>>
>>
>> Send from Lenovo A788t.
Paul E. McKenney wrote:
>On Fri, Oct 24, 2014 at 03:02:04PM -0700, Jay Vosburgh wrote:
>> Paul E. McKenney wrote:
>>
[...]
>> I've got an ftrace capture from unmodified -net, it looks like
>> this:
>>
>> ovs-vswitchd-902 [000] 471.778441: rcu_barrier: rcu_sched Begin
>> cpu
I believe the intent of the code was to drop oldest bytes from the queue,
not the latest if we drop one byte and both latest and some oldest of we
are dropping more than one.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/vsxxxaa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Davidlohr Bueso
The i_mmap_rwsem protects shared pages against races
when doing the sharing and unsharing, ultimately
calling huge_pmd_share/unshare() for PMD pages --
it also needs it to avoid races when populating the pud
for pmd allocation when looking for a shareable pmd page
for
Removes skein_debug.h include since skein_debug.h is nonexistent.
Signed-off-by: Eric Rost
---
drivers/staging/skein/skein_base.h | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/staging/skein/skein_base.h
b/drivers/staging/skein/skein_base.h
index
Removes unneeded #define SKEIN_PORT_CODE since skein_port.h is
nonexistent.
Signed-off-by: Eric Rost
---
drivers/staging/skein/skein_base.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/skein/skein_base.c
b/drivers/staging/skein/skein_base.c
index e0994ea..ebc436a 100644
Adds loadable module support to the Skein Hashing Algorithm driver.
Signed-off-by: Eric Rost
---
drivers/staging/skein/Kconfig | 2 +-
drivers/staging/skein/Makefile| 13 +++--
drivers/staging/skein/skein_generic.c | 19 ++-
3 files changed, 26
Inlines the rotl_64 macro.
Signed-off-by: Eric Rost
---
drivers/staging/skein/skein_base.h | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/skein/skein_base.h
b/drivers/staging/skein/skein_base.h
index 9f10af9..0111fa4 100644
---
Adds CryptoAPI support to the Skein Hashing Algorithm driver.
Signed-off-by: Eric Rost
---
drivers/staging/skein/Makefile| 3 +-
drivers/staging/skein/skein_base.h| 5 +
drivers/staging/skein/skein_generic.c | 199 ++
3 files changed, 206
Renames skein.c to skein_base.c and skein.h to skein_base.h in
preparation for naming loadable module skein.ko
Signed-off-by: Eric Rost
---
drivers/staging/skein/Makefile | 2 +-
drivers/staging/skein/skein_api.h | 2 +-
drivers/staging/skein/{skein.c =>
Paul E. McKenney wrote:
>On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
>> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
>> > On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
>> > > On Fri-10/24/14-2014 10:20, Paul E. McKenney wrote:
>
>[ . . . ]
>
>> > > >
Daniel Baluta schrieb am 09.10.2014 14:39:
> From: Irina Tirdea
>
> These changes are needed to support the functionality of a pedometer.
> A pedometer has two basic functionalities: step counter and step detector.
>
> The step counter needs to be enabled and then it will count the steps
> in
Adds CryptoAPI and loadable module support to the Skein Hashing
Algorithm. Collapses threefish module into skein module. Renames skein.c
and skein.h to skein_base.c and skein_base.h so module can be named
skein.ko. Inlines rotl_64 macro. Removes unneeded #define and
skein_debug.h include.
Eric
Collapses threefish module into skein module.
Signed-off-by: Eric Rost
---
drivers/staging/skein/Kconfig | 22 +++---
drivers/staging/skein/Makefile | 11 +--
2 files changed, 8 insertions(+), 25 deletions(-)
diff --git a/drivers/staging/skein/Kconfig
Coverity pointed out that at return point error is always 0 so the
conditional is not needed.
Signed-off-by: Dmitry Torokhov
---
drivers/input/misc/ims-pcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/misc/ims-pcu.c b/drivers/input/misc/ims-pcu.c
index
On Fri, Oct 24, 2014 at 2:54 PM, Paolo Bonzini wrote:
> On 10/24/2014 07:57 PM, Andy Lutomirski wrote:
>> > KVM_EXIT_UNKNOWN is a kvm bug, we don't really know whether it was
>> > triggered by a priveledged application. Let's not kill the guest: WARN
>> > and inject #UD instead.
>>
>> This
On 10/24/2014 03:09 PM, Andreas Dilger wrote:
> On Oct 24, 2014, at 9:10 AM, Dmitry Vyukov wrote:
>> On Fri, Oct 24, 2014 at 7:04 PM, Sasha Levin wrote:
>>> On 10/24/2014 09:42 AM, Peter Zijlstra wrote:
On Fri, Oct 24, 2014 at 09:23:35AM -0400, Sasha Levin wrote:
>
> i >> 32 may
On 10/24/2014 02:05 PM, One Thousand Gnomes wrote:
> On Fri, 24 Oct 2014 19:10:49 +0400
> Dmitry Vyukov wrote:
>
>> On Fri, Oct 24, 2014 at 7:04 PM, Sasha Levin wrote:
>>> On 10/24/2014 09:42 AM, Peter Zijlstra wrote:
On Fri, Oct 24, 2014 at 09:23:35AM -0400, Sasha Levin wrote:
>
>
On Fri, Oct 24, 2014 at 03:02:04PM -0700, Jay Vosburgh wrote:
> Paul E. McKenney wrote:
>
> >On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
> >> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
> >> > On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
> >> > > On
On Fri, Oct 24, 2014 at 5:41 AM, Vince Weaver wrote:
> On Thu, 23 Oct 2014, Peter Zijlstra wrote:
>
>> On Tue, Oct 21, 2014 at 01:05:49PM -0400, Vince Weaver wrote:
>
>> > There are various reasons why you might want to start events at times
>> > other than the beginning of the program. Some
On Oct 24, 2014, at 9:10 AM, Dmitry Vyukov wrote:
> On Fri, Oct 24, 2014 at 7:04 PM, Sasha Levin wrote:
>> On 10/24/2014 09:42 AM, Peter Zijlstra wrote:
>>> On Fri, Oct 24, 2014 at 09:23:35AM -0400, Sasha Levin wrote:
i >> 32 may happen to be "i", but is there anything that prevents
Various parts of the kernel acquire and release this mutex,
so add i_mmap_lock_write() and immap_unlock_write() helper
functions that will encapsulate this logic. The next patch
will make use of these.
Signed-off-by: Davidlohr Bueso
Reviewed-by: Rik van Riel
---
include/linux/fs.h | 10
Both register and unregister call build_map_info() in order
to create the list of mappings before installing or removing
breakpoints for every mm which maps file backed memory. As
such, there is no reason to hold the i_mmap_rwsem exclusively,
so share it and allow concurrent readers to build the
Shrinking/truncate logic can call nommu_shrink_inode_mappings()
to verify that any shared mappings of the inode in question aren't
broken (dead zone). afaict the only user being ramfs to handle
the size change attribute.
Pretty much a no-brainer to share the lock.
Signed-off-by: Davidlohr Bueso
No brainer conversion: collect_procs_file() only schedules
a process for later kill, share the lock, similarly to
the anon vma variant.
Signed-off-by: Davidlohr Bueso
---
mm/memory-failure.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/memory-failure.c
As per the comment in move_ptes(), we only require taking the
anon vma and i_mmap locks to ensure that rmap will always observe
either the old or new ptes, in the case of need_rmap_lock=true.
No modifications to the tree itself, thus share the i_mmap_rwsem.
Signed-off-by: Davidlohr Bueso
---
Am Freitag, 24. Oktober 2014, 14:42:06 schrieb Doug Anderson:
> Now that SPI DMA has been fixed on rk3288 we can enable it.
>
> Signed-off-by: Doug Anderson
> Signed-off-by: Alexandru M Stan
applied into my v3.19-armsoc/dts branch
I've taken the liberty of changing the subject to
ARM:
The i_mmap_mutex is a close cousin of the anon vma lock,
both protecting similar data, one for file backed pages
and the other for anon memory. To this end, this lock can
also be a rwsem. In addition, there are some important
opportunities to share the lock when there are no tree
modifications.
__xip_unmap() will remove the xip sparse page from the cache
and take down pte mapping, without altering the interval tree,
thus share the i_mmap_rwsem when searching for the ptes to
unmap.
Additionally, tidy up the function a bit and make variables only
local to the interval tree walk loop.
Convert all open coded mutex_lock/unlock calls to the
i_mmap_[lock/unlock]_write() helpers.
Signed-off-by: Davidlohr Bueso
Acked-by: Rik van Riel
---
fs/hugetlbfs/inode.c| 4 ++--
kernel/events/uprobes.c | 4 ++--
kernel/fork.c | 4 ++--
mm/filemap_xip.c| 4 ++--
Similarly to the anon memory counterpart, we can share
the mapping's lock ownership as the interval tree is
not modified when doing doing the walk, only the file
page.
Signed-off-by: Davidlohr Bueso
Acked-by: Rik van Riel
---
include/linux/fs.h | 10 ++
mm/rmap.c | 6 +++---
Hello,
This series is a continuation of the conversion of the
i_mmap_mutex to rwsem, following what we have for the
anon memory counterpart. With Hugh's feedback from the
first iteration (sorry about leaving this fall behind for
so long, but I've just finally had time to re-look at this
-- see
On Fri, Oct 24, 2014 at 04:53:27PM -0400, Waiman Long wrote:
> The additional register pressure may just cause a few more register moves
> which should be negligible in the overall performance . The additional
> icache pressure, however, may have some impact on performance. I was trying
> to
Paul E. McKenney wrote:
>On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
>> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
>> > On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
>> > > On Fri-10/24/14-2014 10:20, Paul E. McKenney wrote:
>
>[ . . . ]
>
>> > > >
On Fri, Oct 24, 2014 at 5:18 PM, Mark Brown wrote:
> On Fri, Oct 24, 2014 at 04:36:24PM -0400, Rob Clark wrote:
>
>> iirc, I was using _get_exclusive() in a few places where I wanted to
>> be sure not to get dummy-regulator in cases where I should
>> -EPROBE_DEFER instead (since probe order with
On 10/24/2014 07:57 PM, Andy Lutomirski wrote:
> > KVM_EXIT_UNKNOWN is a kvm bug, we don't really know whether it was
> > triggered by a priveledged application. Let's not kill the guest: WARN
> > and inject #UD instead.
>
> This scares me a bit. For guest CPL3, it's probably okay. For guest
>
On Sat, Oct 25, 2014 at 12:25:57AM +0300, Yanko Kaneti wrote:
> On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
> > On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
> > > On Fri-10/24/14-2014 10:20, Paul E. McKenney wrote:
[ . . . ]
> > > > Well, if you are feeling aggressive,
On Tuesday, October 21, 2014 11:08:59 PM Rafael J. Wysocki wrote:
> Hi Everyone,
>
> This is version 6 of the unified device properties interface patchset.
>
> The original cover letter from Mika is here:
>
> http://marc.info/?l=devicetree=141087052200600=4
>
> and my cover letters for
z...@rock-chips.com writes:
> From: Chris Zhong
>
> It's a basic version of suspend and resume for rockchip, it only support
> RK3288
> now.
>
> Signed-off-by: Tony Xie
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v3:
> - move the pinmux of gpio6_c6 save and restore to pinctrl-rockchip
To help people transition, accept the 'xip' mount option (and report it
in /proc/mounts), but print a message encouraging people to switch over
to the 'dax' option.
Signed-off-by: Matthew Wilcox
Reviewed-by: Mathieu Desnoyers
---
Documentation/filesystems/ext2.txt | 5 +++--
fs/ext2/ext2.h
From: Matthew Wilcox
Since this is relating to FS_XIP, not KERNEL_XIP, it should be called
DAX instead of XIP.
Signed-off-by: Matthew Wilcox
---
drivers/block/Kconfig | 13 +++--
drivers/block/brd.c | 14 +++---
2 files changed, 14 insertions(+), 13 deletions(-)
diff --git
From: Rafael J. Wysocki
Provide a way for device drivers using GPIOs described by ACPI
GpioIo resources in _CRS to tell the GPIO subsystem what names
(connection IDs) to associate with specific GPIO pins defined
in there.
To do that, a driver needs to define a mapping table as a
NULL-terminated
On Mon, Oct 20, 2014 at 07:46:05AM +0100, Lee Jones wrote:
> On Sat, 18 Oct 2014, Linus Walleij wrote:
>
> > This adds the register offsets for pull up/down for the STMPE
> > 1601, 1801 and 24xx expanders. This is used to bias GPIO lines
> > and keypad lines.
> >
> > Signed-off-by: Linus Walleij
Now that SPI DMA has been fixed on rk3288 we can enable it.
Signed-off-by: Doug Anderson
Signed-off-by: Alexandru M Stan
---
arch/arm/boot/dts/rk3288.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index
On Friday, October 24, 2014 10:34:36 AM Mika Westerberg wrote:
> On Thu, Oct 23, 2014 at 11:51:59PM +0200, Rafael J. Wysocki wrote:
> > OK, let's try to take that a bit farther. :-)
> >
> > With the (untested) patch below applied (which is a replacement for the one
> > sent previously), the
When I was adjusting patch in 848d479361793edb79aa68140cb64d4ec9032d88 to
use devm_ioremap_resource() I messed it up.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/opencores-kbd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Jan Kara pointed out that calling ext2_xip_verify_sb() in ext2_remount()
doesn't make sense, since changing the XIP option on remount isn't
allowed. It also doesn't make sense to re-check whether blocksize is
supported since it can't change between mounts.
Replace the call to
DAX is a replacement for the variation of XIP currently supported by
the ext2 filesystem. We have three different things in the tree called
'XIP', and the new focus is on access to data rather than executables,
so a name change was in order. DAX stands for Direct Access. The X is
for eXciting.
Replace ext2_use_xip() with test_opt(XIP) which expands to the same code
Signed-off-by: Matthew Wilcox
Reviewed-by: Mathieu Desnoyers
---
fs/ext2/ext2.h | 4
fs/ext2/inode.c | 2 +-
fs/ext2/namei.c | 4 ++--
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/fs/ext2/ext2.h
On Fri-10/24/14-2014 11:32, Paul E. McKenney wrote:
> On Fri, Oct 24, 2014 at 08:35:26PM +0300, Yanko Kaneti wrote:
> > On Fri-10/24/14-2014 10:20, Paul E. McKenney wrote:
> > > On Fri, Oct 24, 2014 at 08:09:31PM +0300, Yanko Kaneti wrote:
> > > > On Fri-10/24/14-2014 09:54, Paul E. McKenney
Pagecache faults recheck i_size after taking the page lock to ensure that
the fault didn't race against a truncate. We don't have a page to lock
in the XIP case, so use the i_mmap_mutex instead. It is locked in the
truncate path in unmap_mapping_range() after updating i_size. So while
we hold
This is practically generic code; other filesystems will want to call
it from other places, but there's nothing ext2-specific about it.
Make it a little more generic by allowing it to take a count of the number
of bytes to zero rather than fixing it to a single page. Thanks to Dave
Hansen for
In order to support accesses to larger chunks of memory, pass in a
'size' parameter (counted in bytes), and return the amount available at
that address.
Add a new helper function, bdev_direct_access(), to handle common
functionality including partition handling, checking the length requested
is
1 - 100 of 1488 matches
Mail list logo
