On Fri, Feb 7, 2014 at 3:10 PM, Chris Mason <c...@fb.com> wrote: > On Fri 07 Feb 2014 07:10:38 AM EST, Fengguang Wu wrote: >> >> On Fri, Feb 07, 2014 at 02:13:59AM -0800, David Rientjes wrote: >>> >>> On Fri, 7 Feb 2014, Fengguang Wu wrote: >>> >>>> [ 1.625020] BTRFS: selftest: Running btrfs_split_item tests >>>> [ 1.627004] BTRFS: selftest: Running find delalloc tests >>>> [ 2.289182] tsc: Refined TSC clocksource calibration: 2299.967 MHz >>>> [ 292.084537] kthreadd invoked oom-killer: gfp_mask=0x3000d0, order=1, >>>> oom_score_adj=0 >>>> [ 292.086439] kthreadd cpuset= >>>> [ 292.087072] BUG: unable to handle kernel NULL pointer dereference at >>>> 0000000000000038 >>>> [ 292.087372] IP: [<ffffffff812119de>] pr_cont_kernfs_name+0x1b/0x6c >>> >>> >>> This looks like a problem with the cpuset cgroup name, are you sure this >>> isn't related to the removal of cgroup->name? >> >> >> It looks not related to patch "cgroup: remove cgroup->name", because >> that patch lies in the cgroup tree and not contained in output of "git log >> BAD_COMMIT". > > > Still not sure exactly what is going on, but I can't trigger it here. My > first guess is that it is related to having btrfs static, some part of our > init is happening at the wrong time, and the self tests are swooping in and > causing trouble.
I couldn't reproduce it either so far, neither on a physical machine nor in a vm (qemu+kvm) (with CONFIG_BTRFS_FS=y, CONFIG_CRYPTO_CRC32C=y and CONFIG_CRYPTO_CRC32C_INTEL=y). If you disable CONFIG_BTRFS_FS_RUN_SANITY_TESTS, does it still crash? thanks > > -- Filipe David Manana, "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men." -- 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/