From: Dave Chinner <david@fromorbit.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Ben Myers <bpm@sgi.com>, Dave Chinner <dchinner@redhat.com>,
linux-fsdevel@vger.kernel.org,
"ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>
Subject: Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003
Date: Thu, 10 Oct 2013 15:28:20 +1100 [thread overview]
Message-ID: <20131010042820.GA5663@dastard> (raw)
In-Reply-To: <20131010033834.GA13141@localhost>
On Thu, Oct 10, 2013 at 11:38:34AM +0800, Fengguang Wu wrote:
> On Thu, Oct 10, 2013 at 11:33:00AM +0800, Fengguang Wu wrote:
> > On Thu, Oct 10, 2013 at 11:26:37AM +0800, Fengguang Wu wrote:
> > > Dave,
> > >
> > > > I note that you have CONFIG_SLUB=y, which means that the cache slabs
> > > > are shared with objects of other types. That means that the memory
> > > > corruption problem is likely to be caused by one of the other
> > > > filesystems that is probing the block device(s), not XFS.
> > >
> > > Good to know that, it would easy to test then: just turn off every
> > > other filesystems. I'll try it right away.
> >
> > Seems that we don't even need to do that. A dig through the oops
> > database and I find stack dumps from other FS.
> >
> > This happens in the kernel with same kconfig and commit 3.12-rc1.
>
> Here is a summary of all FS with oops:
>
> 411 ocfs2_fill_super
> 189 xfs_fs_fill_super
> 86 jfs_fill_super
> 50 isofs_fill_super
> 33 fat_fill_super
> 18 vfat_fill_super
> 15 msdos_fill_super
> 11 ext2_fill_super
> 10 ext3_fill_super
> 3 reiserfs_fill_super
The order of probing on the original dmesg output you reported is:
ext3
ext2
fatfs
reiserfs
gfs2
isofs
ocfs2
which means that no XFS filesystem was mounted in the original bug
report, and hence that further indicates that XFS is not responsible
for the problem and that perhaps the original bisect was not
reliable...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-10 4:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 7:39 [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003 Fengguang Wu
2013-10-10 0:59 ` Dave Chinner
2013-10-10 1:16 ` Fengguang Wu
2013-10-10 1:41 ` Fengguang Wu
2013-10-10 3:15 ` Dave Chinner
2013-10-10 3:26 ` Fengguang Wu
2013-10-10 3:33 ` Fengguang Wu
2013-10-10 3:38 ` Fengguang Wu
2013-10-10 4:28 ` Dave Chinner [this message]
2013-10-10 6:03 ` Fengguang Wu
2013-10-10 8:06 ` Dave Chinner
2013-10-10 8:23 ` Fengguang Wu
2013-10-10 9:58 ` Dave Chinner
2013-10-10 6:23 ` Fengguang Wu
2013-10-10 7:29 ` Fengguang Wu
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=20131010042820.GA5663@dastard \
--to=david@fromorbit.com \
--cc=bpm@sgi.com \
--cc=dchinner@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=xfs@oss.sgi.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).