From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jeremiah Mahler
<jmmahler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cgroup: BUG: unable to handle kernel NULL pointer dereference
Date: Sat, 2 Jan 2016 06:54:37 -0500 [thread overview]
Message-ID: <20160102115437.GE3660@htj.duckdns.org> (raw)
In-Reply-To: <20160101234028.GA1750-ZO/ZziT/ZXRSq9BJjBFyUp/QNRX+jHPU@public.gmane.org>
On Fri, Jan 01, 2016 at 03:40:28PM -0800, Jeremiah Mahler wrote:
> all,
>
> When running the latest linux-next (20151231) two of my machines
> hang early in the boot sequence. The initial message is for a
> NULL pointer dereference.
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000030
>
> And the RIP line refers to cgroup_path.
>
> RIP [<ffffffff810eb178>] cgroup_path+0x30/0x80
>
> Attached are pictures of the back trace.
>
> Let me know if I can do anything else to help. I will investigate the
> problem further if I get a chance.
This is most likely from the recent changes from cgroup ns support.
Reverted the patchset for now as it also introduced a bisectability
issue. Serge, can you please look into this one?
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Jeremiah Mahler <jmmahler@gmail.com>,
cgroups@vger.kernel.org, Serge Hallyn <serge.hallyn@ubuntu.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: cgroup: BUG: unable to handle kernel NULL pointer dereference
Date: Sat, 2 Jan 2016 06:54:37 -0500 [thread overview]
Message-ID: <20160102115437.GE3660@htj.duckdns.org> (raw)
In-Reply-To: <20160101234028.GA1750@hudson.localdomain>
On Fri, Jan 01, 2016 at 03:40:28PM -0800, Jeremiah Mahler wrote:
> all,
>
> When running the latest linux-next (20151231) two of my machines
> hang early in the boot sequence. The initial message is for a
> NULL pointer dereference.
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000030
>
> And the RIP line refers to cgroup_path.
>
> RIP [<ffffffff810eb178>] cgroup_path+0x30/0x80
>
> Attached are pictures of the back trace.
>
> Let me know if I can do anything else to help. I will investigate the
> problem further if I get a chance.
This is most likely from the recent changes from cgroup ns support.
Reverted the patchset for now as it also introduced a bisectability
issue. Serge, can you please look into this one?
Thanks.
--
tejun
next parent reply other threads:[~2016-01-02 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160101234028.GA1750@hudson.localdomain>
[not found] ` <20160101234028.GA1750-ZO/ZziT/ZXRSq9BJjBFyUp/QNRX+jHPU@public.gmane.org>
2016-01-02 11:54 ` Tejun Heo [this message]
2016-01-02 11:54 ` cgroup: BUG: unable to handle kernel NULL pointer dereference Tejun Heo
[not found] ` <20160102115437.GE3660-piEFEHQLUPpN0TnZuCh8vA@public.gmane.org>
2016-01-02 18:24 ` Serge E. Hallyn
2016-01-02 18:24 ` Serge E. Hallyn
2016-01-02 21:50 ` Jeremiah Mahler
[not found] ` <20160102215049.GA18564-ZO/ZziT/ZXRSq9BJjBFyUp/QNRX+jHPU@public.gmane.org>
2016-01-03 0:59 ` Serge E. Hallyn
2016-01-03 0:59 ` Serge E. Hallyn
[not found] ` <20160103005916.GA5956-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2016-01-03 3:41 ` Serge E. Hallyn
2016-01-03 3:41 ` Serge E. Hallyn
2016-01-04 19:15 ` Serge E. Hallyn
2016-01-04 19:15 ` Serge E. Hallyn
[not found] ` <20160104191553.GA21384-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2016-01-04 19:17 ` Tejun Heo
2016-01-04 19:17 ` Tejun Heo
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=20160102115437.GE3660@htj.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jmmahler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.