From: Fengguang Wu <fengguang.wu@intel.com>
To: Li Zefan <lizefan@huawei.com>
Cc: Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [cgroup_init_early] WARNING: at mm/percpu.c:292 pcpu_mem_zalloc()
Date: Fri, 14 Jun 2013 09:36:07 +0800 [thread overview]
Message-ID: <20130614013607.GA13366@localhost> (raw)
In-Reply-To: <51BA6DFD.6060903@huawei.com>
On Fri, Jun 14, 2013 at 09:12:29AM +0800, Li Zefan wrote:
> On 2013/6/14 7:00, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
> > commit f284b77333b1320491f138b76f11006bbc962569
> > Author: Tejun Heo <tj@kernel.org>
> > Date: Wed Jun 12 13:50:58 2013 -0700
> >
> > cgroup: use percpu refcnt for cgroup_subsys_states
> >
>
> You were testing the old patch, and Tejun has had it updated yesterday,
> and the new one won't trigger this warning.
Got it, thanks for the quick fix!
Thanks,
Fengguang
prev parent reply other threads:[~2013-06-14 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 23:00 [cgroup_init_early] WARNING: at mm/percpu.c:292 pcpu_mem_zalloc() Fengguang Wu
2013-06-14 1:12 ` Li Zefan
2013-06-14 1:36 ` Fengguang Wu [this message]
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=20130614013607.GA13366@localhost \
--to=fengguang.wu@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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