From: Andy Whitcroft <apw@canonical.com>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Pitt <martin.pitt@ubuntu.com>
Subject: cgroup pids controller -- WARN_ON_ONCE triggering
Date: Tue, 8 Dec 2015 14:58:51 +0000 [thread overview]
Message-ID: <20151208145851.GJ9837@bark> (raw)
The commit below attempts to fix up pid controller charging:
commit afcf6c8b75444382e0f9996157207ebae34a8848
Author: Tejun Heo <tj@kernel.org>
Date: Thu Oct 15 16:41:53 2015 -0400
cgroup: add cgroup_subsys->free() method and use it to fix pids controller
Since this change we are seeing system hangs in early boot on multiple
architecures. We have a console log on ppc64el [1] which fingers
pids_cancel(). Manual debugging on amd64 VMs seems to indicate that we
are now tripping the WARN_ON_ONCE() below:
static void pids_cancel(struct pids_cgroup *pids, int num)
{
/*
* A negative count (or overflow for that matter) is invalid,
* and indicates a bug in the `pids` controller proper.
*/
WARN_ON_ONCE(atomic64_add_negative(-num, &pids->counter));
}
Converting this to a printk I was able to obtain confirmation that we are
indeed seeing this go negative in some cases.
Reverting the above commit seems to resolve the early boot issues in
my testing.
-apw
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523586
next reply other threads:[~2015-12-08 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 14:58 Andy Whitcroft [this message]
2015-12-08 15:24 ` cgroup pids controller -- WARN_ON_ONCE triggering Tejun Heo
2015-12-08 17:05 ` Andy Whitcroft
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=20151208145851.GJ9837@bark \
--to=apw@canonical.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=martin.pitt@ubuntu.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