From: Tejun Heo <tj@kernel.org>
To: lizefan@huawei.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>
Subject: [PATCH 3/4] cgroup: use restart_syscall() for retries after offline waits in cgroup_subtree_control_write()
Date: Tue, 6 May 2014 07:50:43 -0400 [thread overview]
Message-ID: <1399377044-29873-4-git-send-email-tj@kernel.org> (raw)
In-Reply-To: <1399377044-29873-1-git-send-email-tj@kernel.org>
After waiting for a child to finish offline,
cgroup_subtree_control_write() jumps up to retry from after the input
parsing and active protection breaking. This retry makes the
scheduled locking update more difficult. Let's simplify it by
returning with restart_syscall() for retries.
Signed-off-by: Tejun Heo <tj@kernel.org>
---
kernel/cgroup.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 9066fe9..3ced79a 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -2535,7 +2535,7 @@ out_finish:
static int cgroup_subtree_control_write(struct cgroup_subsys_state *dummy_css,
struct cftype *cft, char *buffer)
{
- unsigned int enable_req = 0, disable_req = 0, enable, disable;
+ unsigned int enable = 0, disable = 0;
struct cgroup *cgrp = dummy_css->cgroup, *child;
struct cgroup_subsys *ss;
char *tok, *p;
@@ -2552,11 +2552,11 @@ static int cgroup_subtree_control_write(struct cgroup_subsys_state *dummy_css,
continue;
if (*tok == '+') {
- enable_req |= 1 << ssid;
- disable_req &= ~(1 << ssid);
+ enable |= 1 << ssid;
+ disable &= ~(1 << ssid);
} else if (*tok == '-') {
- disable_req |= 1 << ssid;
- enable_req &= ~(1 << ssid);
+ disable |= 1 << ssid;
+ enable &= ~(1 << ssid);
} else {
return -EINVAL;
}
@@ -2574,9 +2574,6 @@ static int cgroup_subtree_control_write(struct cgroup_subsys_state *dummy_css,
*/
cgroup_get(cgrp);
kernfs_break_active_protection(cgrp->control_kn);
-retry:
- enable = enable_req;
- disable = disable_req;
mutex_lock(&cgroup_tree_mutex);
@@ -2606,7 +2603,9 @@ retry:
schedule();
finish_wait(&child->offline_waitq, &wait);
cgroup_put(child);
- goto retry;
+
+ ret = restart_syscall();
+ goto out_unbreak;
}
/* unavailable or not enabled on the parent? */
@@ -2690,6 +2689,7 @@ out_unlock:
mutex_unlock(&cgroup_mutex);
out_unlock_tree:
mutex_unlock(&cgroup_tree_mutex);
+out_unbreak:
kernfs_unbreak_active_protection(cgrp->control_kn);
cgroup_put(cgrp);
return ret;
--
1.9.0
next prev parent reply other threads:[~2014-05-06 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:50 [PATCHSET cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates Tejun Heo
2014-05-06 11:50 ` [PATCH 1/4] cgroup: fix offlining child waiting in cgroup_subtree_control_write() Tejun Heo
2014-05-06 11:50 ` [PATCH 2/4] cgroup: only allow space as the separator for "cgroup.subtree_control" Tejun Heo
2014-05-06 13:22 ` [PATCH v2 2/9] cgroup: update and fix parsing of "cgroup.subtree_control" Tejun Heo
2014-05-06 11:50 ` Tejun Heo [this message]
2014-05-06 11:50 ` [PATCH 4/4] cgroup: use release_agent_path_lock in cgroup_release_agent_show() 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=1399377044-29873-4-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--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