diff options
author | Hugh Dickins <hughd@google.com> | 2013-08-28 16:31:23 -0700 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2013-08-29 11:05:07 -0400 |
commit | bb78a92f47696b2da49f2692b6a9fa56d07c444a (patch) | |
tree | 6750776493dcfd0cd180b7fc0a666406708547c8 /drivers/parport | |
parent | c95389b4cd6a4b52af78bea706a274453e886251 (diff) | |
download | linux-bb78a92f47696b2da49f2692b6a9fa56d07c444a.tar.bz2 |
cgroup: fix rmdir EBUSY regression in 3.11
On 3.11-rc we are seeing cgroup directories left behind when they should
have been removed. Here's a trivial reproducer:
cd /sys/fs/cgroup/memory
mkdir parent parent/child; rmdir parent/child parent
rmdir: failed to remove `parent': Device or resource busy
It's because cgroup_destroy_locked() (step 1 of destruction) leaves
cgroup on parent's children list, letting cgroup_offline_fn() (step 2 of
destruction) remove it; but step 2 is run by work queue, which may not
yet have removed the children when parent destruction checks the list.
Fix that by checking through a non-empty list of children: if every one
of them has already been marked CGRP_DEAD, then it's safe to proceed:
those children are invisible to userspace, and should not obstruct rmdir.
(I didn't see any reason to keep the cgrp->children checks under the
unrelated css_set_lock, so moved them out.)
tj: Flattened nested ifs a bit and updated comment so that it's
correct on both for-3.11-fixes and for-3.12.
Signed-off-by: Hugh Dickins <hughd@google.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'drivers/parport')
0 files changed, 0 insertions, 0 deletions