From: Jens Axboe <jaxboe@fusionio.com>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nilfs2: fix oops due to a bad aops initialization
Date: Wed, 30 Mar 2011 09:47:00 +0200 [thread overview]
Message-ID: <4D92DFF4.9030801@fusionio.com> (raw)
In-Reply-To: <20110330.132555.158630340.ryusuke@osrg.net>
On 2011-03-30 06:25, Ryusuke Konishi wrote:
> I've found a regression of nilfs2 file system in 2.6.39-rc1.
>
> The recent per-queue plugging removal patch causes kernel oopses in
> nilfs. The following patch will fix this.
>
> I'll send it to Linus along with other bug-fixes.
Irk, I guess we need the empty aops then.
You can add my acked-by to the patch, sorry about that.
--
Jens Axboe
next prev parent reply other threads:[~2011-03-30 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 4:25 [PATCH] nilfs2: fix oops due to a bad aops initialization Ryusuke Konishi
2011-03-30 7:47 ` Jens Axboe [this message]
2011-03-30 11:07 ` Jens Axboe
2011-03-30 11:17 ` Jens Axboe
2011-03-30 11:48 ` Ryusuke Konishi
2011-03-30 11:51 ` Jens Axboe
2011-03-30 11:22 ` Ryusuke Konishi
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=4D92DFF4.9030801@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
/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