[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1191616252.3861.5.camel@localhost.localdomain>
Date: Fri, 05 Oct 2007 13:30:52 -0700
From: Mingming Cao <cmm@...ibm.com>
To: Badari Pulavarty <pbadari@...il.com>
Cc: Valerie Clement <valerie.clement@...l.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: 2.6.23-rc9: Oops in cache_alloc_refill() mm/slab.c
On Fri, 2007-10-05 at 07:54 -0700, Badari Pulavarty wrote:
> 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.
>
It's unlikely to be the jbd_slab_cleanup.patch, which actually get rid
of slab allocation for buffers passing down to disk IO, and replace with
get_free_page directly.
Could you send me the profile used for ffsb test?
Thanks,
Mingming
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists