From: David Howells <dhowells@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: dhowells@redhat.com, Vegard Nossum <vegard.nossum@gmail.com>,
Serge Hallyn <serue@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Eric Sesterhenn <snakebyte@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>,
containers@lists.osdl.org
Subject: Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload
Date: Wed, 11 Feb 2009 12:54:06 +0000 [thread overview]
Message-ID: <27972.1234356846@redhat.com> (raw)
In-Reply-To: <20090211212208.C3C6.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro <kosaki.motohiro@jp.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
next prev parent reply other threads:[~2009-02-11 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 5:41 [CRED bug?] 2.6.29-rc3 don't survive on stress workload KOSAKI Motohiro
2009-02-10 7:10 ` Vegard Nossum
2009-02-10 7:28 ` KOSAKI Motohiro
2009-02-11 3:56 ` Vegard Nossum
2009-02-11 10:48 ` David Howells
2009-02-10 12:18 ` Ingo Molnar
2009-02-11 12:25 ` KOSAKI Motohiro
2009-02-11 12:54 ` David Howells [this message]
2009-02-10 10:35 ` David Howells
2009-02-10 10:49 ` KOSAKI Motohiro
2009-02-11 12:41 ` David Howells
2009-02-11 12:52 ` KOSAKI Motohiro
2009-02-11 13:09 ` David Howells
2009-02-11 14:04 ` KOSAKI Motohiro
2009-02-11 16:33 ` Ingo Molnar
2009-02-11 17:07 ` David Howells
2009-02-11 17:19 ` Ingo Molnar
2009-02-12 11:09 ` David Howells
2009-02-12 11:23 ` KOSAKI Motohiro
2009-02-12 12:04 ` David Howells
2009-02-12 14:39 ` Serge E. Hallyn
2009-02-12 17:18 ` David Howells
2009-02-13 4:44 ` KOSAKI Motohiro
2009-02-13 8:28 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27972.1234356846@redhat.com \
--to=dhowells@redhat.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=snakebyte@gmx.de \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox