From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Bastien ROUCARIES <roucaries.bastien@gmail.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Frantisek Hanzlik <franta@hanzlici.cz>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: fs/fs-writeback oopses in kernel 2.6.33.4-95.fc13.i686.PAE
Date: Wed, 7 Jul 2010 14:14:31 -0700 [thread overview]
Message-ID: <20100707141431.079a46b0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100707210209.GA24063@lst.de>
On Wed, 7 Jul 2010 23:02:09 +0200
Christoph Hellwig <hch@lst.de> wrote:
> On Wed, Jul 07, 2010 at 01:51:18PM -0700, Andrew Morton wrote:
> > 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?
>
> I have no idea what oops you mean.
http://lmgtfy.com/?q=fs%2Ffs-writeback+oopses+in+kernel+2.6.33.4-95.fc13.i686.PAE
> But the writeback code is very
> different now compared to 2.6.33, and with the latest fixes in Jens'
> tree there are no known issues left. (know to me anyway)
Well the issue is that 2.6.33.x goes oops and we'd like to fix that.
if it's fixed in current mainline then which patch did it?
next prev parent reply other threads:[~2010-07-07 21:14 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
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 [this message]
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=20100707141431.079a46b0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dmonakhov@openvz.org \
--cc=franta@hanzlici.cz \
--cc=hch@lst.de \
--cc=kyle@mcmartin.ca \
--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