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
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
