Re: 2.6.18 ext3 panic.

Dave Jones
2006-10-03T06:40:48Z

On Mon, Oct 02, 2006 at 11:19:45PM -0700, Andrew Morton wrote:
> On Tue, 03 Oct 2006 00:43:01 -0500
> Eric Sandeen <sandeen@sandeen.net> wrote:
>
> > Dave Jones wrote:
> >
> > > So I managed to reproduce it with an 'fsx foo' and a
> > > 'fsstress -d . -r -n 100000 -p 20 -r'. This time I grabbed it from
> > > a vanilla 2.6.18 with none of the Fedora patches..
> > >
> > > I'll give 2.6.18-git a try next.
> > >
> > > Dave
> > >
> > > ----------- [cut here ] --------- [please bite here ] ---------
> > > Kernel BUG at fs/buffer.c:2791
> >
> > I had thought/hoped that this was fixed by Jan's patch at
> > http://lkml.org/lkml/2006/9/7/236 from the thread started at
> > http://lkml.org/lkml/2006/9/1/149, but it seems maybe not. Dave hit this bug
> > first by going through that new codepath....
>
> Yes, Jan's patch is supposed to fix that !buffer_mapped() assertion. iirc,
> Badari was hitting that BUG and was able to confirm that Jan's patch
> (3998b9301d3d55be8373add22b6bc5e11c1d9b71 in post-2.6.18 mainline) fixed
> it.

Ok, this afternoon I was definitly running a kernel with that patch in it,
and managed to get a trace (It was the one from the top of this thread
that unfortunatly got truncated).

Now, I can't reproduce it on a plain 2.6.18+that patch.
I'll leave the stress test running overnight, and see if anything
falls out in the morning.

Dave

--