All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, Ben Myers <bpm@sgi.com>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
	Dave Chinner <dchinner@redhat.com>
Subject: Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003
Date: Thu, 10 Oct 2013 11:26:37 +0800	[thread overview]
Message-ID: <20131010032637.GA12725@localhost> (raw)
In-Reply-To: <20131010031515.GT4446@dastard>

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.

Thanks,
Fengguang

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Dave Chinner <dchinner@redhat.com>,
	linux-fsdevel@vger.kernel.org, Ben Myers <bpm@sgi.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003
Date: Thu, 10 Oct 2013 11:26:37 +0800	[thread overview]
Message-ID: <20131010032637.GA12725@localhost> (raw)
In-Reply-To: <20131010031515.GT4446@dastard>

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.

Thanks,
Fengguang

  reply	other threads:[~2013-10-10  3:26 UTC|newest]

Thread overview: 35+ 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  0:59   ` Dave Chinner
2013-10-10  0:59   ` Dave Chinner
2013-10-10  1:16   ` Fengguang Wu
2013-10-10  1:16     ` Fengguang Wu
2013-10-10  1:41     ` Fengguang Wu
2013-10-10  1:41       ` Fengguang Wu
2013-10-10  3:15       ` Dave Chinner
2013-10-10  3:15         ` Dave Chinner
2013-10-10  3:26         ` Fengguang Wu [this message]
2013-10-10  3:26           ` Fengguang Wu
2013-10-10  3:33           ` Fengguang Wu
2013-10-10  3:33             ` [Ocfs2-devel] " Fengguang Wu
2013-10-10  3:33             ` Fengguang Wu
2013-10-10  3:38             ` Fengguang Wu
2013-10-10  3:38               ` [Ocfs2-devel] " Fengguang Wu
2013-10-10  3:38               ` Fengguang Wu
2013-10-10  4:28               ` Dave Chinner
2013-10-10  4:28                 ` [Ocfs2-devel] " Dave Chinner
2013-10-10  4:28                 ` Dave Chinner
2013-10-10  6:03                 ` Fengguang Wu
2013-10-10  6:03                   ` [Ocfs2-devel] " Fengguang Wu
2013-10-10  6:03                   ` Fengguang Wu
2013-10-10  8:06                   ` Dave Chinner
2013-10-10  8:07                     ` [Ocfs2-devel] " Dave Chinner
2013-10-10  8:06                     ` Dave Chinner
2013-10-10  8:23                     ` Fengguang Wu
2013-10-10  8:24                       ` [Ocfs2-devel] " Fengguang Wu
2013-10-10  9:58                       ` Dave Chinner
2013-10-10  9:58                         ` [Ocfs2-devel] " Dave Chinner
2013-10-10  9:58                         ` Dave Chinner
2013-10-10  6:23   ` Fengguang Wu
2013-10-10  7:29     ` 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=20131010032637.GA12725@localhost \
    --to=fengguang.wu@intel.com \
    --cc=bpm@sgi.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.