From: Badari Pulavarty Subject: Re: 2.6.23-rc9: Oops in cache_alloc_refill() mm/slab.c Date: Fri, 05 Oct 2007 07:54:17 -0700 Message-ID: <1191596057.6106.106.camel@dyn9047017100.beaverton.ibm.com> References: <4705113A.7030908@bull.net> <1191534231.6106.99.camel@dyn9047017100.beaverton.ibm.com> <47063EF3.4050302@bull.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , ext4 development , cmm@us.ibm.com To: Valerie Clement Return-path: Received: from e36.co.us.ibm.com ([32.97.110.154]:55105 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756313AbXJEOvK (ORCPT ); Fri, 5 Oct 2007 10:51:10 -0400 In-Reply-To: <47063EF3.4050302@bull.net> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Fri, 2007-10-05 at 15:41 +0200, Valerie Clement wrote: > Badari Pulavarty wrote: > > On Thu, 2007-10-04 at 18:13 +0200, Valerie Clement wrote: > >> While running ffsb tests on my ext4 filesystem, I got an Oops in > >> cache_alloc_refill(). > >> I turned on SLAB debugging and here is the message I got: > >> > >> slab: Internal list corruption detected in cache 'buffer_head'(30), > >> slabp ffff81007e100100(1515870810). Hexdump: > > > > slabp->inuse = 1515870810 looks bogus. Is this easily reproducible ? > > Hi Badari, > Thanks for your answer. > I didn't reproduce it without the latest ext4 patches. So I suspect a > bug in one of them. > But how debugging this? > Which other debug traces can I turn on? Let me understand. You applied latest ext4 patchsets ? If so, Mingming has some slab-cleanup changes in the patchset. You can try backing them out and see. Thanks, Badari