From: Roman Gushchin <guroan@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, Roman Gushchin <guro@fb.com>
Subject: [PATCH v3 3/7] cgroup: protect cgroup->nr_(dying_)descendants by css_set_lock
Date: Fri, 16 Nov 2018 16:38:26 -0800 [thread overview]
Message-ID: <20181117003830.15344-4-guro@fb.com> (raw)
In-Reply-To: <20181117003830.15344-1-guro@fb.com>
Now the number of descendant cgroups and the number of dying
descendant cgroups are synchronized using the cgroup_mutex.
The number of descendant cgroups will be required by the cgroup v2
freezer, which will use it to determine if a cgroup is frozen
(depending on total number of descendants and number of frozen
descendants). It's not always acceptable to grab the cgroup_mutex,
especially from quite hot paths (e.g. exit()).
To avoid this, let's additionally synchronize these counters
using the css_set_lock.
Signed-off-by: Roman Gushchin <guro@fb.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: kernel-team@fb.com
---
include/linux/cgroup-defs.h | 3 +++
kernel/cgroup/cgroup.c | 20 ++++++++++++++++----
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/include/linux/cgroup-defs.h b/include/linux/cgroup-defs.h
index 22254c1fe1c5..9e77559c7f49 100644
--- a/include/linux/cgroup-defs.h
+++ b/include/linux/cgroup-defs.h
@@ -346,6 +346,9 @@ struct cgroup {
* Dying cgroups are cgroups which were deleted by a user,
* but are still existing because someone else is holding a reference.
* max_descendants is a maximum allowed number of descent cgroups.
+ *
+ * nr_descendants and nr_dying_descendants are protected
+ * by css_set_lock.
*/
int nr_descendants;
int nr_dying_descendants;
diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
index ef3442555b32..2241cb1d1238 100644
--- a/kernel/cgroup/cgroup.c
+++ b/kernel/cgroup/cgroup.c
@@ -3409,11 +3409,15 @@ static int cgroup_events_show(struct seq_file *seq, void *v)
static int cgroup_stat_show(struct seq_file *seq, void *v)
{
struct cgroup *cgroup = seq_css(seq)->cgroup;
+ int nr_descendants, nr_dying_descendants;
- seq_printf(seq, "nr_descendants %d\n",
- cgroup->nr_descendants);
- seq_printf(seq, "nr_dying_descendants %d\n",
- cgroup->nr_dying_descendants);
+ spin_lock_irq(&css_set_lock);
+ nr_descendants = cgroup->nr_descendants;
+ nr_dying_descendants = cgroup->nr_dying_descendants;
+ spin_unlock_irq(&css_set_lock);
+
+ seq_printf(seq, "nr_descendants %d\n", nr_descendants);
+ seq_printf(seq, "nr_dying_descendants %d\n", nr_dying_descendants);
return 0;
}
@@ -4684,9 +4688,11 @@ static void css_release_work_fn(struct work_struct *work)
if (cgroup_on_dfl(cgrp))
cgroup_rstat_flush(cgrp);
+ spin_lock_irq(&css_set_lock);
for (tcgrp = cgroup_parent(cgrp); tcgrp;
tcgrp = cgroup_parent(tcgrp))
tcgrp->nr_dying_descendants--;
+ spin_unlock_irq(&css_set_lock);
cgroup_idr_remove(&cgrp->root->cgroup_idr, cgrp->id);
cgrp->id = -1;
@@ -4899,12 +4905,14 @@ static struct cgroup *cgroup_create(struct cgroup *parent)
if (ret)
goto out_idr_free;
+ spin_lock_irq(&css_set_lock);
for (tcgrp = cgrp; tcgrp; tcgrp = cgroup_parent(tcgrp)) {
cgrp->ancestor_ids[tcgrp->level] = tcgrp->id;
if (tcgrp != cgrp)
tcgrp->nr_descendants++;
}
+ spin_unlock_irq(&css_set_lock);
if (notify_on_release(parent))
set_bit(CGRP_NOTIFY_ON_RELEASE, &cgrp->flags);
@@ -4956,6 +4964,7 @@ static bool cgroup_check_hierarchy_limits(struct cgroup *parent)
lockdep_assert_held(&cgroup_mutex);
+ spin_lock_irq(&css_set_lock);
for (cgroup = parent; cgroup; cgroup = cgroup_parent(cgroup)) {
if (cgroup->nr_descendants >= cgroup->max_descendants)
goto fail;
@@ -4968,6 +4977,7 @@ static bool cgroup_check_hierarchy_limits(struct cgroup *parent)
ret = true;
fail:
+ spin_unlock_irq(&css_set_lock);
return ret;
}
@@ -5187,10 +5197,12 @@ static int cgroup_destroy_locked(struct cgroup *cgrp)
if (parent && cgroup_is_threaded(cgrp))
parent->nr_threaded_children--;
+ spin_lock_irq(&css_set_lock);
for (tcgrp = cgroup_parent(cgrp); tcgrp; tcgrp = cgroup_parent(tcgrp)) {
tcgrp->nr_descendants--;
tcgrp->nr_dying_descendants++;
}
+ spin_unlock_irq(&css_set_lock);
cgroup1_check_for_release(parent);
--
2.17.2
next prev parent reply other threads:[~2018-11-17 0:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 0:38 [PATCH v3 0/7] freezer for cgroup v2 Roman Gushchin
2018-11-17 0:38 ` [PATCH v3 1/7] cgroup: rename freezer.c into legacy_freezer.c Roman Gushchin
2018-11-17 0:38 ` [PATCH v3 2/7] cgroup: implement __cgroup_task_count() helper Roman Gushchin
2018-11-17 0:38 ` Roman Gushchin [this message]
2018-11-20 16:18 ` [PATCH v3 3/7] cgroup: protect cgroup->nr_(dying_)descendants by css_set_lock Tejun Heo
2018-11-17 0:38 ` [PATCH v3 4/7] cgroup: cgroup v2 freezer Roman Gushchin
2018-11-20 16:25 ` Tejun Heo
2018-11-20 16:33 ` Roman Gushchin
2018-11-20 16:36 ` Tejun Heo
2018-11-20 16:43 ` Roman Gushchin
2018-11-20 16:48 ` Tejun Heo
2018-11-20 17:39 ` Roman Gushchin
2018-11-20 18:05 ` Tejun Heo
2018-11-17 0:38 ` [PATCH v3 5/7] kselftests: cgroup: don't fail on cg_kill_all() error in cg_destroy() Roman Gushchin
2018-11-17 0:38 ` Roman Gushchin
2018-11-17 0:38 ` guroan
2018-11-17 0:38 ` [PATCH v3 6/7] kselftests: cgroup: add freezer controller self-tests Roman Gushchin
2018-11-17 0:38 ` Roman Gushchin
2018-11-17 0:38 ` guroan
2018-11-17 0:38 ` [PATCH v3 7/7] cgroup: document cgroup v2 freezer interface Roman Gushchin
2018-11-17 8:02 ` Mike Rapoport
2018-11-19 17:42 ` Roman Gushchin
2018-11-20 14:06 ` Mike Rapoport
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=20181117003830.15344-4-guro@fb.com \
--to=guroan@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.