From: Tejun Heo <tj@kernel.org>
To: Kenny Yu <kennyyu@fb.com>
Cc: lizefan@huawei.com, hannes@cmpxchg.org, cyphar@cyphar.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH v3] cgroup: Add pids controller event when fork fails because of pid limit
Date: Tue, 21 Jun 2016 13:12:12 -0400 [thread overview]
Message-ID: <20160621171212.GL3262@mtj.duckdns.org> (raw)
In-Reply-To: <1466528198-3416939-1-git-send-email-kennyyu@fb.com>
Hello,
Just a couple nits.
On Tue, Jun 21, 2016 at 09:56:38AM -0700, Kenny Yu wrote:
> Summary:
No need for "Summary:" tag.
> This patch adds more visibility into the pids controller when the controller
> rejects a fork request. Whenever fork fails because the limit on the number of
> pids in the cgroup is reached, the controller will log this and also notify the
> newly added cgroups events file. The `max` key in the events file represents
> the number of times fork failed because of the pids controller.
>
> This change also adds an atomic boolean to prevent logging too much (e.g. a fork
> bomb). The message is logged once per cgroup until the next time the pids limit
> changes.
The above paragraph isn't uptodate anymore.
> @@ -213,10 +220,23 @@ static int pids_can_fork(struct task_struct *task)
> {
> struct cgroup_subsys_state *css;
> struct pids_cgroup *pids;
> + int err;
> + int events_limit;
>
> css = task_css_check(current, pids_cgrp_id, true);
> pids = css_pids(css);
> - return pids_try_charge(pids, 1);
> + err = pids_try_charge(pids, 1);
> + if (err) {
> + events_limit = atomic64_inc_return(&pids->events_limit);
> + cgroup_file_notify(&pids->events_file);
> + /* Only log the first time events_limit is incremented. */
> + if (events_limit == 1) {
> + pr_info("cgroup: fork rejected by pids controller in ");
> + pr_cont_cgroup_path(task_cgroup(current, pids_cgrp_id));
> + pr_cont("\n");
> + }
> + }
> + return err;
> }
It'd be better to use atomic64_inc_and_test() instead.
if (err) {
if (atomic64_inc_and_test()) {
pr_xxx...;
}
cgroup_file_notify(&pids->events_file);
}
Thanks.
--
tejun
next prev parent reply other threads:[~2016-06-21 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 3:09 [PATCH] cgroup: Add pids controller event when fork fails because of pid limit Kenny Yu
2016-06-21 4:44 ` Johannes Weiner
2016-06-21 16:01 ` [PATCH v2] " Kenny Yu
2016-06-21 16:07 ` Aleksa Sarai
2016-06-21 16:34 ` Tejun Heo
2016-06-21 16:56 ` [PATCH v3] " Kenny Yu
2016-06-21 17:12 ` Tejun Heo [this message]
2016-06-21 17:23 ` Kenny Yu
2016-06-21 17:28 ` Tejun Heo
2016-06-21 17:44 ` [PATCH v4] " Kenny Yu
2016-06-21 18:06 ` Tejun Heo
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=20160621171212.GL3262@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=hannes@cmpxchg.org \
--cc=kennyyu@fb.com \
--cc=kernel-team@fb.com \
--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