> >So threading init will work just fine. The only case that will blow up >is calling exec from something that is not the thread group leader. >i.e. If tgid == 1 but pid != 1 the kernel will cause pid == 1 to exit. Should not it, at its best, replace the whole thread group by the new program and have things carry on? Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- References:
- [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- From: Andrew Morton <[email protected]>
- Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- From: [email protected] (Eric W. Biederman)
- [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- Prev by Date: Re: [2.6 patch] make CONFIG_SECCOMP default to n
- Next by Date: Re: [PATCH 2.6.16-rc1-git4] accessfs: a permission managing filesystem
- Previous by thread: Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- Next by thread: Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
- Index(es):
 |