From: "Richard W.M. Jones" <rjones@redhat.com>
To: Chris Mason <clm@fb.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: Sun, 9 Feb 2014 18:47:32 +0000	[thread overview]
Message-ID: <20140209184732.GB7373@redhat.com> (raw)
In-Reply-To: <20140205122120.GW1346@redhat.com>
On Wed, Feb 05, 2014 at 12:21:20PM +0000, Richard W.M. Jones wrote:
> On Tue 04 Feb 2014 12:31:56 PM EST, Richard W.M. Jones wrote:
> >https://lkml.org/lkml/2014/2/4/107
> 
> Sorry about the delay.  I ran into a different kernel bug which
> needed fixing first.
> 
> The patch above *does not* fix this issue.
To follow up here, it's actually an MD problem.  The following
userspace commands are enough to trigger the NULL pointer deref:
  mdadm --create --run test --level raid1 --raid-devices 2 /dev/sda1 /dev/sdb1
  wipefs -a --force /dev/md/test
  mke2fs -t ext4 -F /dev/md/test
There's a full log attached to this comment:
  https://bugzilla.redhat.com/show_bug.cgi?id=1061339#c8
Rich.
-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
next prev parent reply	other threads:[~2014-02-09 18: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
2014-02-05 12:21       ` Richard W.M. Jones
2014-02-09 18:47         ` Richard W.M. Jones [this message]
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=20140209184732.GB7373@redhat.com \
    --to=rjones@redhat.com \
    --cc=axboe@fb.com \
    --cc=clm@fb.com \
    --cc=kmo@daterainc.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).