[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151223165423.GJ5003@mtj.duckdns.org>
Date: Wed, 23 Dec 2015 11:54:23 -0500
From: "tj@...nel.org" <tj@...nel.org>
To: "Alex Ng (LIS)" <alexng@...rosoft.com>
Cc: "lizefan@...wei.com" <lizefan@...wei.com>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [OOPS] BUG_ON in cgroups on 4.4.0-rc5-next
Hello, Alex.
On Tue, Dec 22, 2015 at 07:06:41PM +0000, Alex Ng (LIS) wrote:
> > Can you please let me know the steps to reproduce the bug?
>
> I tried this on a Hyper-V VM hosted in Windows Server 2012R2 and ran
> the attached script. The script clones the linux-next tree in a
> random directory under /tmp in a tight loop.
>
> This panic is not always reproducible, and I have only hit it once
> after running the script about 10 times. A different kernel panic
> happens each time I run this script; and the panics always happen
> during the first iteration of the loop.
Heh, I don't get it. The script doesn't do anything cgroup specific.
Can you please apply the attached patch, reproduce the issue and
report the kernel log?
Thanks.
--
tejun
View attachment "dbg" of type "text/plain" (1138 bytes)
Powered by blists - more mailing lists