Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-05-20 Thread Vivek Goyal
On Mon, Apr 29, 2013 at 09:29:52AM -0400, Vivek Goyal wrote: > On Mon, Apr 29, 2013 at 01:57:18AM -0700, Michel Lespinasse wrote: > > On Mon, Apr 15, 2013 at 6:27 PM, Hugh Dickins wrote: > > > On Mon, 15 Apr 2013, Michel Lespinasse wrote: > > >> sys_brk() passes the length as the difference of two

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-29 Thread Vivek Goyal
On Mon, Apr 29, 2013 at 01:57:18AM -0700, Michel Lespinasse wrote: > On Mon, Apr 15, 2013 at 6:27 PM, Hugh Dickins wrote: > > On Mon, 15 Apr 2013, Michel Lespinasse wrote: > >> sys_brk() passes the length as the difference of two page aligned > >> addresses, so it's fine. But vm_brk() doesn't - i

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-29 Thread Michel Lespinasse
On Mon, Apr 15, 2013 at 6:27 PM, Hugh Dickins wrote: > On Mon, 15 Apr 2013, Michel Lespinasse wrote: >> sys_brk() passes the length as the difference of two page aligned addresses, >> so it's fine. But vm_brk() doesn't - it calls do_brk() which page aligns the >> length, but then vm_brk passes t

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Hugh Dickins
On Mon, 15 Apr 2013, Michel Lespinasse wrote: > On Mon, Apr 15, 2013 at 2:47 PM, Hugh Dickins wrote: > > --- 3.9-rc7/mm/mlock.c 2013-04-01 09:08:05.736012852 -0700 > > +++ linux/mm/mlock.c2013-04-15 14:20:24.454773245 -0700 > > @@ -397,8 +397,7 @@ int __mm_populate(unsigned long start, u > >

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Michel Lespinasse
On Mon, Apr 15, 2013 at 2:47 PM, Hugh Dickins wrote: > --- 3.9-rc7/mm/mlock.c 2013-04-01 09:08:05.736012852 -0700 > +++ linux/mm/mlock.c2013-04-15 14:20:24.454773245 -0700 > @@ -397,8 +397,7 @@ int __mm_populate(unsigned long start, u > long ret = 0; > > VM_BUG_ON(start & ~PAG

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Hugh Dickins
On Mon, 15 Apr 2013, Vivek Goyal wrote: > On Mon, Apr 15, 2013 at 01:59:29PM -0400, Vivek Goyal wrote: > > On Mon, Apr 15, 2013 at 01:34:24PM -0400, Vivek Goyal wrote: > > > On Mon, Apr 15, 2013 at 12:35:52PM -0400, Vivek Goyal wrote: > > > > > > [..] > > > > > My first guess would be that mmap_se

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Vivek Goyal
On Mon, Apr 15, 2013 at 01:59:29PM -0400, Vivek Goyal wrote: > CCing akpm. > > Vivek > > On Mon, Apr 15, 2013 at 01:34:24PM -0400, Vivek Goyal wrote: > > On Mon, Apr 15, 2013 at 12:35:52PM -0400, Vivek Goyal wrote: > > > > [..] > > > > My first guess would be that mmap_sem is held during exec, s

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Vivek Goyal
CCing akpm. Vivek On Mon, Apr 15, 2013 at 01:34:24PM -0400, Vivek Goyal wrote: > On Mon, Apr 15, 2013 at 12:35:52PM -0400, Vivek Goyal wrote: > > [..] > > > My first guess would be that mmap_sem is held during exec, so you > > > can't have __mm_populate() try holding it recursively. > > > > I t

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Vivek Goyal
On Mon, Apr 15, 2013 at 12:35:52PM -0400, Vivek Goyal wrote: [..] > > My first guess would be that mmap_sem is held during exec, so you > > can't have __mm_populate() try holding it recursively. > > I think it is not mmap_sem as even with VM_LOCKED, we take mmap_sem > and things are fine. > > S

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-15 Thread Vivek Goyal
On Fri, Apr 12, 2013 at 07:31:32PM -0700, Michel Lespinasse wrote: > Sorry for the earlier message getting sent before I was done typing it. > > On Fri, Apr 12, 2013 at 11:13 AM, Vivek Goyal wrote: > > Hi, > > > > I am writing some code where I lock down a process memory at exec() time. > > My pa

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-12 Thread Michel Lespinasse
Sorry for the earlier message getting sent before I was done typing it. On Fri, Apr 12, 2013 at 11:13 AM, Vivek Goyal wrote: > Hi, > > I am writing some code where I lock down a process memory at exec() time. > My patches were working fine till 3.9-rc4 and suddendly things broke down > in 3.9-rc5

Re: 3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-12 Thread Michel Lespinasse
On Fri, Apr 12, 2013 at 11:13 AM, Vivek Goyal wrote: > Hi, > > I am writing some code where I lock down a process memory at exec() time. > My patches were working fine till 3.9-rc4 and suddendly things broke down > in 3.9-rc5. > > Whenever I tried to exec() a process with memory locked down, my ba

3.9-rc5: Encountedred INFO: rcu_sched self-detected stall on CPU due to 09a9f1d27

2013-04-12 Thread Vivek Goyal
Hi, I am writing some code where I lock down a process memory at exec() time. My patches were working fine till 3.9-rc4 and suddendly things broke down in 3.9-rc5. Whenever I tried to exec() a process with memory locked down, my bash session hangs and after a while I get following warning. logi