Searched hist:"3 f17da699431ec48540beabc55c54d4b5e66c8e7" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/kernel/ |
| H A D | fork.c | diff 3f17da699431ec48540beabc55c54d4b5e66c8e7 Wed Feb 15 13:13:24 CST 2006 Oleg Nesterov <oleg@tv-sign.ru> [PATCH] fix kill_proc_info() vs CLONE_THREAD race
There is a window after copy_process() unlocks ->sighand.siglock
and before it adds the new thread to the thread list.
In that window __group_complete_signal(SIGKILL) will not see the
new thread yet, so this thread will start running while the whole
thread group was supposed to exit.
I beleive we have another good reason to place attach_pid(PID/TGID)
under ->sighand.siglock. We can do the same for
release_task()->__unhash_process()
de_thread()->switch_exec_pids()
After that we don't need tasklist_lock to iterate over the thread
list, and we can simplify things, see for example do_sigaction()
or sys_times().
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Roland McGrath <roland@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
|