From: "tj@kernel.org" <tj@kernel.org>
To: "Alex Ng (LIS)" <alexng@microsoft.com>
Cc: "lizefan@huawei.com" <lizefan@huawei.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] BUG_ON in cgroups on 4.4.0-rc5-next
Date: Mon, 21 Dec 2015 16:56:18 -0500 [thread overview]
Message-ID: <20151221215618.GB25997@mtj.duckdns.org> (raw)
In-Reply-To: <BLUPR0301MB200140C023EB8C2B414F6B13D8E10@BLUPR0301MB2001.namprd03.prod.outlook.com>
Hello, Alex.
On Fri, Dec 18, 2015 at 08:08:03PM +0000, Alex Ng (LIS) wrote:
> Hi,
>
> I was running a "git clone" of the linux-next source tree and hit the following BUG_ON condition. My box is running kernel 4.4.0-rc5-next-20151217-52.27. Any ideas on how to pin down the cause?
>
> The trace indicates that the following condition in compare_css_sets() triggered the oops:
Can you please let me know the steps to reproduce the bug?
Thanks.
--
tejun
next prev parent reply other threads:[~2015-12-21 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 20:08 Alex Ng (LIS)
2015-12-21 21:56 ` tj [this message]
2015-12-22 19:06 ` Alex Ng (LIS)
2015-12-23 16:54 ` tj
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=20151221215618.GB25997@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=alexng@microsoft.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
/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
all inboxes | Powered by JetHome®