From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Cong Wang'" <xiyou.wangcong@gmail.com>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441 cgroup_get+0x4b/0x50
Date: Fri, 30 Jun 2017 07:31:06 -0400 [thread overview]
Message-ID: <001c01d2f194$5d5e2330$181a6990$@lucidpixels.com> (raw)
In-Reply-To: <CAM_iQpU5Zxfv8vKJwkAF02bgLK=Lyv=kXC9ECmQRoA-yvK8ang@mail.gmail.com>
> -----Original Message-----
> From: Cong Wang [mailto:xiyou.wangcong@gmail.com]
> Sent: Thursday, June 29, 2017 9:44 PM
> To: Justin Piszcz
> Cc: LKML
> Subject: Re: WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
> cgroup_get+0x4b/0x50
>
> On Thu, Jun 29, 2017 at 12:26 AM, Justin Piszcz <jpiszcz@lucidpixels.com
[ snip ]
> >
> > [22606.516656] ------------[ cut here ]------------
> > [22606.516669] WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
> > cgroup_get+0x4b/0x50
> > [22606.516672] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.11.0 #1
> > [22606.516674] Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2
> > 01/16/2015
> > [22606.516676] Call Trace:
> > [22606.516678] <IRQ>
> > [22606.516681] dump_stack+0x4d/0x66
> > [22606.516684] __warn+0xbc/0xe0
> > [22606.516686] warn_slowpath_null+0x18/0x20
> > [22606.516687] cgroup_get+0x4b/0x50
> > [22606.516689] cgroup_sk_alloc+0x56/0x60
>
> This should be fixed by:
>
> commit a590b90d472f2c176c140576ee3ab44df7f67839
> Author: Tejun Heo <tj@kernel.org>
> Date: Fri Apr 28 15:14:55 2017 -0400
>
> cgroup: fix spurious warnings on cgroup_is_dead() from cgroup_sk_alloc()
>
Thank you, patch applied and in production!
Justin.
prev parent reply other threads:[~2017-06-30 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:26 Justin Piszcz
2017-06-30 1:43 ` Cong Wang
2017-06-30 11:31 ` Justin Piszcz [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='001c01d2f194$5d5e2330$181a6990$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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®