| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003 |
| From: | Fengguang Wu <fengguang.wu@xxxxxxxxx> |
| Date: | Thu, 10 Oct 2013 11:26:37 +0800 |
| Cc: | Dave Chinner <dchinner@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, Ben Myers <bpm@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20131010031515.GT4446@dastard> |
| References: | <20131009073910.GA387@localhost> <20131010005900.GE2025@xxxxxxxxxxxxxxxxx> <20131010011640.GA5726@localhost> <20131010014117.GA6017@localhost> <20131010031515.GT4446@dastard> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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 |
| Previous by Date: | Re: [PATCH 2/2] xfs_fsr: create extent-based attr to grow forkoff, Eric Sandeen |
|---|---|
| Next by Date: | Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003, Fengguang Wu |
| Previous by Thread: | Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003, Dave Chinner |
| Next by Thread: | Re: [XFS on bad superblock] BUG: unable to handle kernel NULL pointer dereference at 00000003, Fengguang Wu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |