From: Tejun Heo <tj@kernel.org>
To: lizefan@huawei.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCHSET cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates
Date: Tue, 6 May 2014 07:50:40 -0400 [thread overview]
Message-ID: <1399377044-29873-1-git-send-email-tj@kernel.org> (raw)
Hello,
This patchset contains the following four patches.
0001-cgroup-fix-offlining-child-waiting-in-cgroup_subtree.patch
0002-cgroup-only-allow-space-as-the-separator-for-cgroup..patch
0003-cgroup-use-restart_syscall-for-retries-after-offline.patch
0004-cgroup-use-release_agent_path_lock-in-cgroup_release.patch
0001 fixes two bugs in cgroup_subtree_control_write().
0002 makes subtree_control parsing stricter.
0003 simplifies cgroup_substree_control_write() retry path by using
restart_syscall().
0004 makes cgroup_release_agent_show() use release_path_lock. The
original conversion missed this one.
This patchset is on top of cgroup/for-3.16 12d3089c192c
("kernel/cpuset.c: convert printk to pr_foo()") and available on the
following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-post-unified-updates
diffstat follows.
kernel/cgroup.c | 33 +++++++++++++++++----------------
1 file changed, 17 insertions(+), 16 deletions(-)
Thanks.
--
tejun
next 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 Tejun Heo [this message]
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 ` [PATCH 3/4] cgroup: use restart_syscall() for retries after offline waits in cgroup_subtree_control_write() Tejun Heo
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-1-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