Revision 2d5516cbb9daf7d0e342a2e3b0fc6f8c39a81205 authored by Oleg Nesterov on 02 March 2009, 21:58:45 UTC, committed by Linus Torvalds on 09 March 2009, 20:23:25 UTC
CLONE_PARENT can fool the ->self_exec_id/parent_exec_id logic. If we
re-use the old parent, we must also re-use ->parent_exec_id to make
sure exit_notify() sees the right ->xxx_exec_id's when the CLONE_PARENT'ed
task exits.

Also, move down the "p->parent_exec_id = p->self_exec_id" thing, to place
two different cases together.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Cc: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Serge E. Hallyn <serge@hallyn.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent df0b4a5
History
File Mode Size
00-INDEX -rw-r--r-- 543 bytes
as-iosched.txt -rw-r--r-- 8.5 KB
barrier.txt -rw-r--r-- 10.6 KB
biodoc.txt -rw-r--r-- 54.5 KB
capability.txt -rw-r--r-- 618 bytes
data-integrity.txt -rw-r--r-- 13.5 KB
deadline-iosched.txt -rw-r--r-- 2.8 KB
ioprio.txt -rw-r--r-- 4.6 KB
queue-sysfs.txt -rw-r--r-- 2.3 KB
request.txt -rw-r--r-- 2.0 KB
stat.txt -rw-r--r-- 3.2 KB
switching-sched.txt -rw-r--r-- 1.6 KB

back to top