On 6/5/2015 9:23 AM, James Long wrote:
Hi Andreas,
My problem is actually with unshare(2), rather than unshare(1). Is
there an equivalent patch for unshare(2)?
I don't think you understood the upstream patch. The idea is that after
unshare(2), calls to mount(2) have the option causing the mount to show
up in other namespaces or not. You seem to have an expectation mismatch
in this regard. If you do not want it to show up in the other
namespace, then you need to mount --make-private.
In other words, this is not a bug in unshare ( 1 or 2 ).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
