diff options
author | Oleg Nesterov <oleg@redhat.com> | 2017-08-21 17:35:02 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-08-24 17:12:21 -0700 |
commit | 322cd32623653c0f860d2fc9789fa5b7ac7b09ae (patch) | |
tree | 451e3f376259633fb8055f9ac8ab919c11bd11b2 /Kbuild | |
parent | 61332dc598c3f223678b2d7192ccf3472c544799 (diff) | |
download | linux-stable-322cd32623653c0f860d2fc9789fa5b7ac7b09ae.tar.gz linux-stable-322cd32623653c0f860d2fc9789fa5b7ac7b09ae.tar.bz2 linux-stable-322cd32623653c0f860d2fc9789fa5b7ac7b09ae.zip |
pids: make task_tgid_nr_ns() safe
commit dd1c1f2f2028a7b851f701fc6a8ebe39dcb95e7c upstream.
This was reported many times, and this was even mentioned in commit
52ee2dfdd4f5 ("pids: refactor vnr/nr_ns helpers to make them safe") but
somehow nobody bothered to fix the obvious problem: task_tgid_nr_ns() is
not safe because task->group_leader points to nowhere after the exiting
task passes exit_notify(), rcu_read_lock() can not help.
We really need to change __unhash_process() to nullify group_leader,
parent, and real_parent, but this needs some cleanups. Until then we
can turn task_tgid_nr_ns() into another user of __task_pid_nr_ns() and
fix the problem.
Reported-by: Troy Kensinger <tkensinger@google.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions