[PATCHSET v2 cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates

From: Tejun Heo
Date: Fri May 09 2014 - 15:34:42 EST


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@xxxxxxxxxx
[1] http://lkml.kernel.org/g/20140507160429.GE26540@xxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/