From: Tejun Heo <tj@kernel.org>
To: lizefan@huawei.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCHSET v2 cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates
Date: Fri, 9 May 2014 15:32:48 -0400 [thread overview]
Message-ID: <1399663975-315-1-git-send-email-tj@kernel.org> (raw)
Hello,
Changes from the last take[L] are,
* 0002, 0003 and 0007 added.
* Other patches are refreshed without content change.
This patchset contains the following seven patches.
0001-cgroup-fix-offlining-child-waiting-in-cgroup_subtree.patch
0002-cgroup-cgroup_idr_lock-should-be-bh.patch
0003-cgroup-css_release-shouldn-t-clear-cgroup-subsys.patch
0004-cgroup-update-and-fix-parsing-of-cgroup.subtree_cont.patch
0005-cgroup-use-restart_syscall-for-retries-after-offline.patch
0006-cgroup-use-release_agent_path_lock-in-cgroup_release.patch
0007-cgroup-rename-css_tryget-to-css_tryget_online.patch
0001 fixes two bugs in cgroup_subtree_control_write().
0004 fixes and makes subtree_control parsing stricter.
0005 simplifies cgroup_substree_control_write() retry path by using
restart_syscall().
0006 makes cgroup_release_agent_show() use release_path_lock. The
original conversion missed this one.
0007 renames css_tryget() to css_tryget_online(). This patch was
posted separately before - [1] - and acked by Michal and Johannes.
This patchset is on top of cgroup/for-3.16 6e1a046e9458 ("Merge branch
'for-3.16' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu
into for-3.16") and available in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-post-unified-updates-v2
diffstat follows.
block/blk-cgroup.c | 2 -
fs/bio.c | 2 -
include/linux/cgroup.h | 14 +++----
kernel/cgroup.c | 88 +++++++++++++++++++++++++------------------------
kernel/cpuset.c | 6 +--
kernel/events/core.c | 3 +
mm/hugetlb_cgroup.c | 2 -
mm/memcontrol.c | 46 +++++++++++++------------
8 files changed, 84 insertions(+), 79 deletions(-)
--
tejun
[L] http://lkml.kernel.org/g/1399377044-29873-1-git-send-email-tj@kernel.org
[1] http://lkml.kernel.org/g/20140507160429.GE26540@htj.dyndns.org
next reply other threads:[~2014-05-09 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 19:32 Tejun Heo [this message]
2014-05-09 19:32 ` [PATCH 1/7] cgroup: fix offlining child waiting in cgroup_subtree_control_write() Tejun Heo
2014-05-09 19:32 ` [PATCH 2/7] cgroup: cgroup_idr_lock should be bh Tejun Heo
2014-05-09 19:32 ` [PATCH 3/7] cgroup: css_release() shouldn't clear cgroup->subsys[] Tejun Heo
2014-05-09 19:32 ` [PATCH 4/7] cgroup: update and fix parsing of "cgroup.subtree_control" Tejun Heo
2014-05-13 3:51 ` Li Zefan
2014-05-13 15:18 ` Tejun Heo
2014-05-09 19:32 ` [PATCH 5/7] cgroup: use restart_syscall() for retries after offline waits in cgroup_subtree_control_write() Tejun Heo
2014-05-13 5:00 ` Li Zefan
2014-05-13 15:19 ` Tejun Heo
2014-05-09 19:32 ` [PATCH 6/7] cgroup: use release_agent_path_lock in cgroup_release_agent_show() Tejun Heo
2014-05-09 19:32 ` [PATCH 7/7] cgroup: rename css_tryget*() to css_tryget_online*() Tejun Heo
2014-05-09 19:47 ` [PATCH v2 " Tejun Heo
2014-05-13 6:35 ` [PATCHSET v2 cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates Li Zefan
2014-05-13 16:12 ` 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=1399663975-315-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
Powered by JetHome