[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27972.1234356846@redhat.com>
Date: Wed, 11 Feb 2009 12:54:06 +0000
From: David Howells <dhowells@...hat.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: dhowells@...hat.com, Vegard Nossum <vegard.nossum@...il.com>,
Serge Hallyn <serue@...ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>,
Eric Sesterhenn <snakebyte@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
containers@...ts.osdl.org
Subject: Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
> f6 : 1003e6b6b6b6b6b6b6b6b f7 : 0ffe6af8e85a500000000
I'd guess you now have CONFIG_DEBUG_SLAB turned on. That looks like slab
poisoning in register f6.
> r17 : 00000000dead4ead r18 : a000000100cd2274 r19 : a000000100d6b6c0
And that looks like SPINLOCK_MAGIC in r17, so I'd guess something just
successfully validated a spinlock, possibly atomic_dec_and_lock() in
free_uid().
This may mean that the user_struct being released is valid, but the
user_namespace it refers to is already released.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists