All of lore.kernel.org
 help / color / mirror / Atom feed
* unshare behavior when polyinstantiating
@ 2007-05-29 13:59 Ted X Toth
  2007-05-29 16:55 ` Daniel J Walsh
  0 siblings, 1 reply; 2+ messages in thread
From: Ted X Toth @ 2007-05-29 13:59 UTC (permalink / raw)
  To: SE Linux

I've run into some polyinstantiation bugs but want to make sure I 
understand what unshare(CLONE_NEWNS) does before I submit a patch. Is it 
the case that the new namespace created by unshare is related to the 
current process and when this process exits the namespace is destroyed 
or is no longer valid? All mounts and unmounts done in the new namespace 
have no affect on the parent processes namespace, correct?

Ted

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-05-29 16:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-29 13:59 unshare behavior when polyinstantiating Ted X Toth
2007-05-29 16:55 ` Daniel J Walsh

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.