From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fengguang Wu 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 Message-ID: <20131010032637.GA12725@localhost> References: <20131009073910.GA387@localhost> <20131010005900.GE2025@devil.localdomain> <20131010011640.GA5726@localhost> <20131010014117.GA6017@localhost> <20131010031515.GT4446@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, Ben Myers , xfs@oss.sgi.com, linux-kernel@vger.kernel.org, Dave Chinner To: Dave Chinner Return-path: Content-Disposition: inline In-Reply-To: <20131010031515.GT4446@dastard> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org 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