From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload Date: Wed, 11 Feb 2009 12:54:06 +0000 Message-ID: <27972.1234356846@redhat.com> References: <20090211212208.C3C6.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20090210142443.629E.KOSAKI.MOTOHIRO@jp.fujitsu.com> <19f34abd0902092310g513fb776s2e4d37285c8fa7be@mail.gmail.com> Return-path: In-Reply-To: <20090211212208.C3C6.KOSAKI.MOTOHIRO@jp.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org To: KOSAKI Motohiro Cc: dhowells@redhat.com, Vegard Nossum , Serge Hallyn , LKML , Lee Schermerhorn , Eric Sesterhenn , Andrew Morton , containers@lists.osdl.org List-Id: containers.vger.kernel.org KOSAKI Motohiro 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