Messages in this thread | | | Date | Fri, 19 Nov 2010 18:25:13 +0200 | Subject | Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch | From | Alexey Dobriyan <> |
| |
On Fri, Nov 19, 2010 at 6:10 PM, Tejun Heo <tj@kernel.org> wrote: > Well, if you ask me, having pidns w/o a way to reinstate PID from > userland is pretty silly
No. Chrome uses CLONE_PID so that exploit couldn't attach to processes in parent pidns.
> and you and I might not know yet but it's > quite imaginable that there will be other use cases for the capability > unlike in-kernel CR. Kernel provides building blocks not the whole > frigging package and for very good reasons.
Speaking of pids, pid's value itself is never interesing (except maybe pid 1). It's a cookie.
CLONE_SET_PID came up only now because only C/R wants it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |