Re: fs/fs-writeback oopses in kernel 2.6.33.4-95.fc13.i686.PAE

[Andrew Morton]

On Thu, 1 Jul 2010 09:54:07 +0200
Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx> wrote:

> On Tue, Jun 15, 2010 at 10:25 AM, Bastien ROUCARIES
> <roucaries.bastien@xxxxxxxxx> wrote:
> > On Mon, Jun 14, 2010 at 9:57 PM, Andrew Morton
> > <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> >> On Thu, 10 Jun 2010 11:06:17 +0200
> >> Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx> wrote:
> >>
> >>> > > I don't see anything which would generate this warning in 2.6.33.4's
> >>> > > fs/fs-writeback.c:597. __RH must have mucked with it.
> >>> > Already fixed in mainstream by
> >>> > commit 7c8a3554c683f512dbcee26faedb42e4c05f12fa
> >>> > Author: Jens Axboe <jens.axboe@xxxxxxxxxx>
> >>> > Date: __ Tue May 18 14:29:29 2010 +0200
> >>>
> >>> Do you send it to stable ? I am hitting the same bug and count is high
> >>> on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
> >>>
> >>
> >> The commit didn't have a cc:stable in the changelog so no, it probably
> >> wasn't backported.
> >>
> >> But that commit was later reverted anyway. __Hopefully when the real fix
> >> gets merged, it will be backported.
> >
> 
> Any news of this bug ?
> 

There have been various dramas in the writeback code recently. 
Christoph has been working on it.

Christoph, is this oops known about, and are those patches expected to
fix it?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/