Messages in this thread |  | | Date | Thu, 28 Nov 2013 16:47:19 +0100 | From | Oleg Nesterov <> | Subject | Re: [PATCH]: exec: avoid propagating PF_NO_SETAFFINITY into userspace child |
| |
On 11/28, Peter Zijlstra wrote: > > So there's three useful parts to having a single parent task: > > - its a task so you can change the entire task attribute set; current > and future.
You can't change, say, its fs->root.
OK, OK, this is almost off-topic, I am just trying to say that (perhaps) in the longer term we might want even more than just a dedicated kernel thread.
> - new children will automatically get the desired attributes.
yes,
> - all children are easily identified by virtual of being children of > said parent process.
Well, UMH_WAIT_PROC won't work in this case, or it will be "single-threaded" too. OK, this is probably solvable, but nontrivial. In this case "khelper" should act as a /sbin/init for user-mode helpers.
Oleg.
|  |