mirror of
https://github.com/Fishwaldo/Star64_linux.git
synced 2025-06-20 05:31:15 +00:00
start the global /sbin/init with 0,0 special pids
As Eric pointed out, there is no problem with init starting with sid == pgid == 0, and this was historical linux behavior changed in 2.6.18. Remove kernel_init()->__set_special_pids(), this is unneeded and complicates the rules for sys_setsid(). This change and the previous change in daemonize() mean that /sbin/init does not need the special "session != 1" hack in sys_setsid() any longer. We can't remove this check yet, we should cleanup copy_process(CLONE_NEWPID) first, so update the comment only. Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Pavel Emelyanov <xemul@openvz.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
297bd42b15
commit
430c623121
2 changed files with 4 additions and 6 deletions
|
@ -833,7 +833,6 @@ static int __init kernel_init(void * unused)
|
|||
*/
|
||||
init_pid_ns.child_reaper = current;
|
||||
|
||||
__set_special_pids(task_pid(current));
|
||||
cad_pid = task_pid(current);
|
||||
|
||||
smp_prepare_cpus(setup_max_cpus);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue