From: Andrew Morton <akpm@linux-foundation.org>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: Dmitry Monakhov <dmonakhov@openvz.org>,
Frantisek Hanzlik <franta@hanzlici.cz>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: fs/fs-writeback oopses in kernel 2.6.33.4-95.fc13.i686.PAE
Date: Mon, 14 Jun 2010 12:57:16 -0700 [thread overview]
Message-ID: <20100614125716.b04fcd28.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTimPwbOga_gEMajfciD8ZokBaz99c2ty9R6q_cs5@mail.gmail.com>
On Thu, 10 Jun 2010 11:06:17 +0200
Bastien ROUCARIES <roucaries.bastien@gmail.com> 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@oracle.com>
> > 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.
next prev parent reply other threads:[~2010-06-14 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 12:37 fs/fs-writeback oopses in kernel 2.6.33.4-95.fc13.i686.PAE Frantisek Hanzlik
2010-05-25 6:05 ` Andrew Morton
2010-05-25 10:35 ` Dmitry Monakhov
2010-06-10 9:06 ` Bastien ROUCARIES
2010-06-14 19:57 ` Andrew Morton [this message]
2010-06-15 8:18 ` Kyle McMartin
2010-06-15 8:25 ` Bastien ROUCARIES
2010-07-01 7:54 ` Bastien ROUCARIES
2010-07-07 20:51 ` Andrew Morton
2010-07-07 21:02 ` Christoph Hellwig
2010-07-07 21:14 ` Andrew Morton
2010-07-07 22:31 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100614125716.b04fcd28.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dmonakhov@openvz.org \
--cc=franta@hanzlici.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=roucaries.bastien@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox