summaryrefslogtreecommitdiff
path: root/crypto/api.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-08-29 17:03:48 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2013-08-29 17:03:48 -0700
commit41615e811b3031728a003da077005e8dcf9d71cc (patch)
tree53a5418d5157e0e58580bda1dd422765baca6317 /crypto/api.c
parentff497452636f4687e517964817b7e2bd99f4b44b (diff)
parentbb78a92f47696b2da49f2692b6a9fa56d07c444a (diff)
Merge branch 'for-3.11-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
Pull cgroup fix from Tejun Heo: "During the percpu reference counting update which was merged during v3.11-rc1, the cgroup destruction path was updated so that a cgroup in the process of dying may linger on the children list, which was necessary as the cgroup should still be included in child/descendant iteration while percpu ref is being killed. Unfortunately, I forgot to update cgroup destruction path accordingly and cgroup destruction may fail spuriously with -EBUSY due to lingering dying children even when there's no live child left - e.g. "rmdir parent/child parent" will usually fail. This can be easily fixed by iterating through the children list to verify that there's no live child left. While this is very late in the release cycle, this bug is very visible to userland and I believe the fix is relatively safe. Thanks Hugh for spotting and providing fix for the issue" * 'for-3.11-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup: cgroup: fix rmdir EBUSY regression in 3.11
Diffstat (limited to 'crypto/api.c')
0 files changed, 0 insertions, 0 deletions