From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Lukas Czerner <lczerner@redhat.com>
Subject: Re: [GIT PULL] Single important block patch for 2.6.38
Date: Mon, 14 Mar 2011 09:19:57 +0100 [thread overview]
Message-ID: <4D7DCFAD.3000704@fusionio.com> (raw)
In-Reply-To: <AANLkTi=NAeBWE28Vygx5Qf+OYgMW2Js180fptQnbbXmw@mail.gmail.com>
On 2011-03-13 23:51, Linus Torvalds wrote:
> On Fri, Mar 11, 2011 at 6:38 AM, Jens Axboe <jaxboe@fusionio.com> wrote:
>>
>> This fixes a regression introduced early in the 2.6.38 series, where
>> blkdev_issue_zeroout() has a nasty race that causes a panic. Thanks to
>> Lukas Czerner for finding and fixing this one. Please pull!
>
> What about the "Null pointer OOPS in sync_inodes_sb" issue due to the
> broken sb->s_bdi setting to NULL?
Sent something out to George to test, hopefully we can close this one
for 2.6.38 in a simple fashion.
--
Jens Axboe
prev parent reply other threads:[~2011-03-14 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:38 [GIT PULL] Single important block patch for 2.6.38 Jens Axboe
2011-03-13 22:51 ` Linus Torvalds
2011-03-14 8:19 ` Jens Axboe [this message]
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=4D7DCFAD.3000704@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=lczerner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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