Pavel Emelyanov [xemul@xxxxxxxxxxxxx] wrote: | > I agree with all the points you and Pavel you talked about but I don't | > feel comfortable to have the current process to switch the pid namespace | > because of the process tree hierarchy (what will be the parent of the | > process when you enter the pid namespace for example). | | The answer is - the one, that used to be. I see no problems with it. | Do you? Just to be clear, when a process unshares its pid namespace, it takes on additional pid nr (== 1) in the new namespace but retains its original pid nr(s) in the parent (ancestor) namespaces right ? i.e the process becomes the container-init of the new namespace. When it exits, all its children belonging to the new namespace are killed too, but any children in the parent namespace (i.e children created before unshare()) are not killed. After the unshare() the process will not be able to signal any children it created before the unshare() (bc their active pid namespaces are different) Sukadev -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
