Remove CLONE_FILES from init kernel thread creation
A message that is not in the archive (sent off-list or not yet received): [email protected]
In message <[email protected]> you write:
Quoted 2 lines
Rusty? Any idea why
call_usermodehelper()usesCLONE_FILES?
Your guess is correct about consolidation. But there is no bug AFAICT.
The "normal" (non-waiting case) uses "CLONE_VFORK | SIGCHLD". The "waiting" case uses "CLONE_KERNEL", but then that thread does another fork with just "SIGCHLD".
ie. the actual thread which does the exec never uses CLONE_FILES.
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.