Pavel Emelyanov wrote: > Cedric Le Goater wrote: >> Pavel Emelyanov wrote: >>> Hi guys! >>> >>> As you might have seen, recently there was some spontaneous >>> discussion about the namespaces-working-together problems. >>> >>> Ted T'so proposed to create some document that describes what >>> problems user may have when he/she creates some new namespace, >>> but keeps others shared. I like this idea, so here's the draft >>> with the problems I currently have in mind and can describe >>> somewhat audibly - the "namespaces compatibility list". >> that compatibility list could be encoded in the way we check >> the clone flags in copy_process() and unshare(). It would >> also be good to have it as a comment somewhere in kernel/fork.c > > How can we insure, that a new task will not share the files > with its parent to address the PID namespaces vs VFS namespaces > interaction? There's no way to do it. We can only keep them in > one IPC namespace... ? I'm not sure I understand you. C. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
