[lkml]   [2008]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.26-rc9: Reported regressions from 2.6.25
On Sun, Jul 06, 2008 at 08:46:09AM -0700, Linus Torvalds wrote:
> > Bug-Entry :
> > Subject : 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0
> > Submitter : Alexey Dobriyan <>
> > Date : 2008-05-27 09:23 (41 days old)
> > References :
> >
> > Handled-By : Oleg Nesterov <>
> > Linus Torvalds <>
> > Paul E. McKenney <>
> > Patch :
> This one is the same thing that is reported as unresolved, and no, I don't
> think that existing patch was ever really tested to fix anything. Paul?

Alexey tested the above patch, and it did not fix his failure
( Neither did the patch
at I was never able to
reproduce Alexey's failure, whether by running LTP in parallel
with 170 kernel builds or by running either in parallel with
rcutorture. Some enhancements to make rcutorture more vicious
were unable to provoke failures.

Alexey is able to provoke the failure on a maxcpus=1 configuration,
which should narrow things down quite a bit. I dug through
assembly, and found no issues at that level.

Alexey, would you be willing to send along your vmlinux or disassembly
of the RCU functions?

In any case, I am working up additional diagnostics.

> I suspect SRCU will need to be simply marked BROKEN for now, because
> nobody knows what the problem Alexey sees is. Apparently it's been seen by
> a few other people too.

PREEMPT_RCU is already marked "default n" with a "Say N if you are
unsure. Shouldn't that cover it?

I don't believe that SRCU is involved, please let me know if I missed

Nick Piggin mentioned seeing failures similar to Alexey's, and I still
need his repeat-by. Nick?

Thanx, Paul

 \ /
  Last update: 2008-08-01 23:13    [W:0.269 / U:0.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site