linux-kernel - Re: [btrfs] BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52F4F755.4090503@fb.com>
Date:	Fri, 7 Feb 2014 10:10:13 -0500
From:	Chris Mason <clm@...com>
To:	Fengguang Wu <fengguang.wu@...el.com>
CC:	Tejun Heo <tj@...nel.org>,
	Filipe David Borba Manana <fdmanana@...il.com>,
	<linux-btrfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: [btrfs] BUG: unable to handle kernel NULL pointer dereference
 at 0000000000000038

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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/