From: Chris Mason <clm@fb.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>, <axboe@fb.com>,
<kmo@daterainc.com>, <neilb@suse.de>
Subject: Re: Latest kernel NULL pointer deref when running mke2fs
Date: Tue, 4 Feb 2014 12:49:11 -0500 [thread overview]
Message-ID: <52F12817.1040003@fb.com> (raw)
In-Reply-To: <20140204173155.GV1346@redhat.com>
On Tue 04 Feb 2014 12:31:56 PM EST, Richard W.M. Jones wrote:
>
> Kent Overstreet pointed me to this patch:
>
> https://lkml.org/lkml/2014/2/4/107
>
> Will test it soon.
>
I don't think this will touch the call path from your oops...at least I
don't see how it helps bio_clone do the right thing.
-chris
next prev parent reply other threads:[~2014-02-04 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 16:09 Latest kernel NULL pointer deref when running mke2fs Richard W.M. Jones
2014-02-04 17:04 ` Chris Mason
2014-02-04 17:16 ` Richard W.M. Jones
2014-02-04 17:31 ` Richard W.M. Jones
2014-02-04 17:49 ` Chris Mason [this message]
2014-02-05 12:21 ` Richard W.M. Jones
2014-02-09 18:47 ` Richard W.M. Jones
2014-02-10 23:08 ` Kent Overstreet
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=52F12817.1040003@fb.com \
--to=clm@fb.com \
--cc=axboe@fb.com \
--cc=kmo@daterainc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rjones@redhat.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;
as well as URLs for NNTP newsgroup(s).