From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752079AbcABSYV (ORCPT ); Sat, 2 Jan 2016 13:24:21 -0500 Received: from h2.hallyn.com ([78.46.35.8]:50272 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751818AbcABSYS (ORCPT ); Sat, 2 Jan 2016 13:24:18 -0500 Date: Sat, 2 Jan 2016 12:24:16 -0600 From: "Serge E. Hallyn" To: Tejun Heo Cc: Jeremiah Mahler , cgroups@vger.kernel.org, Serge Hallyn , Stephen Rothwell , linux-kernel@vger.kernel.org, Dan Williams Subject: Re: cgroup: BUG: unable to handle kernel NULL pointer dereference Message-ID: <20160102182416.GA3957@mail.hallyn.com> References: <20160101234028.GA1750@hudson.localdomain> <20160102115437.GE3660@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160102115437.GE3660@htj.duckdns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 02, 2016 at 06:54:37AM -0500, Tejun Heo wrote: > 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 [] 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? Tried to reproduce with setting CONFIG_CFQ_GROUP_IOSCHED=y, but did not succeed. Could you send me the .config? Also, if someone could send the objdump -d output that might help. Though really, it seems clear that current->nsproxy must be NULL. Hm, that's right - we used to have that issue in pidns (or was it netns) during process exit. I don't know that I'll get time this afternoon, but I'll look into it asap. thanks.