diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2016-07-15 06:35:24 -0500 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2016-07-15 07:56:32 -0400 |
commit | 7bd8830875bfa380c68f390efbad893293749324 (patch) | |
tree | 86f51feccb725f56d42fd3cca7e256a787cfec13 /Documentation/IPMI.txt | |
parent | 82d6489d0fed2ec8a8c48c19e8d8a04ac8e5bb26 (diff) | |
download | talos-op-linux-7bd8830875bfa380c68f390efbad893293749324.tar.gz talos-op-linux-7bd8830875bfa380c68f390efbad893293749324.zip |
cgroupns: Fix the locking in copy_cgroup_ns
If "clone(CLONE_NEWCGROUP...)" is called it results in a nice lockdep
valid splat.
In __cgroup_proc_write the lock ordering is:
cgroup_mutex -- through cgroup_kn_lock_live
cgroup_threadgroup_rwsem
In copy_process the guts of clone the lock ordering is:
cgroup_threadgroup_rwsem -- through threadgroup_change_begin
cgroup_mutex -- through copy_namespaces -- copy_cgroup_ns
lockdep reports some a different call chains for the first ordering of
cgroup_mutex and cgroup_threadgroup_rwsem but it is harder to trace.
This is most definitely deadlock potential under the right
circumstances.
Fix this by by skipping the cgroup_mutex and making the locking in
copy_cgroup_ns mirror the locking in cgroup_post_fork which also runs
during fork under the cgroup_threadgroup_rwsem.
Cc: stable@vger.kernel.org
Fixes: a79a908fd2b0 ("cgroup: introduce cgroup namespaces")
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'Documentation/IPMI.txt')
0 files changed, 0 insertions, 0 deletions