Re: [PATCH -mm 0/9] unshare system call (take 3)

[Ingo Molnar]

* JANAK DESAI <janak@xxxxxxxxxx> wrote:

> Patches are organized as follows:
> 
> 1. Patch implementing system call handler sys_unshare. System call
>    accepts all clone(2) flags but returns -EINVAL when attempt is
>    made to unshare any shared context.
> 2. Patch registering system call for i386 architecture
> 3. Patch registering system call for powerpc architecture
> 4. Patch registering system call for ppc architecture
> 5. Patch registering system call for x86_64 architecture
> 6. Patch implementing unsharing of filesystem information
> 7. Patch implementing unsharing of namespace
> 8. Patch implementing unsharing of vm
> 9. Patch implementing unsharing of files
> 
> Unsharing of singnal handlers is still not implemented. As far as I 
> can tell, issues raised by Chris Wright regarding possible problems 
> stemming from interaction of timers with unsharing of signal handlers, 
> has been resolved by a 2.6.14 patch that fixed race in send_sigqueue 
> with thread exit. However, I do want to understand the code better and 
> experiment with it some more before implementing signal handler 
> unsharing. If deemed ok, it would be easy to add that functionality.

yes, it would be preferrable to have them all at once, once it hits 
upstream. Also, would unsharing the thread group make sense?

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/