From: Chris Mason <clm@fb.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Tejun Heo <tj@kernel.org>,
Filipe David Borba Manana <fdmanana@gmail.com>,
<linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [btrfs] BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
Date: Fri, 7 Feb 2014 10:10:13 -0500 [thread overview]
Message-ID: <52F4F755.4090503@fb.com> (raw)
In-Reply-To: <20140207121038.GA1690@localhost>
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.
next prev parent reply other threads:[~2014-02-07 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140207023801.GC11051@localhost>
2014-02-07 10:13 ` [btrfs] BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 David Rientjes
2014-02-07 12:10 ` Fengguang Wu
2014-02-07 15:10 ` Chris Mason [this message]
2014-02-07 15:22 ` Filipe David Manana
2014-02-08 13:07 ` Fengguang Wu
2014-02-10 9:12 ` Fengguang Wu
2014-02-07 21:13 ` David Rientjes
2014-02-08 20:10 ` Tejun Heo
2014-02-10 9:25 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F4F755.4090503@fb.com \
--to=clm@fb.com \
--cc=fdmanana@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).