From: Richard Weinberger <richard@nod.at>
To: Ram Pai <linuxram@us.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Jeff Mahoney <jeffm@suse.com>,
sahne@0x90.at,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MNT_DETACH and mount namespace issue
Date: Tue, 05 Aug 2014 00:16:10 +0200 [thread overview]
Message-ID: <53E0062A.8030204@nod.at> (raw)
In-Reply-To: <20140804221051.GH24719@ram.oc3035372033.ibm.com>
Am 05.08.2014 00:10, schrieb Ram Pai:
> On Mon, Aug 04, 2014 at 11:19:35PM +0200, Richard Weinberger wrote:
>> Am 04.08.2014 18:46, schrieb Eric W. Biederman:
>>> Richard Weinberger <richard.weinberger@gmail.com> writes:
>>
>> /proc is propagating into another mount namespaces that does not care.
>> This happens because systemd creates for several services a mount namespace and sets
>> the root tree to MS_SHARED.
>
> if propagations are not needed, than set the root of the new mount
> namespace to MS_PRIVATE first and then set it to MS_SHARED.
>
> MS_PRIVATE will delink the propagations, and MS_SHARED later will enable
> the new mounts to propagate to whoever wants them.
AFAICT this would break systemd's PrivateTmp feature. :(
They want propagation. Such that a systemd service has a private /tmp but sees freshly
mounted filesystems after setting up the namespace.
Thanks,
//richard
next prev parent reply other threads:[~2014-08-04 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:59 [PATCH] vfs: Fix RCU usage in __propagate_umount() Richard Weinberger
2014-07-30 14:20 ` Richard Weinberger
2014-07-30 18:39 ` Paul E. McKenney
2014-07-30 18:39 ` Paul E. McKenney
2014-07-30 20:46 ` MNT_DETACH and mount namespace issue (was: Re: [PATCH] vfs: Fix RCU usage in __propagate_umount()) Richard Weinberger
2014-07-31 22:17 ` MNT_DETACH and mount namespace issue Richard Weinberger
2014-08-01 15:44 ` Ram Pai
2014-08-01 19:20 ` Richard Weinberger
2014-08-01 19:20 ` Richard Weinberger
2014-08-01 22:09 ` Eric W. Biederman
2014-08-04 8:40 ` Richard Weinberger
2014-08-04 16:46 ` Eric W. Biederman
2014-08-04 21:19 ` Richard Weinberger
2014-08-04 22:10 ` Ram Pai
2014-08-04 22:16 ` Richard Weinberger [this message]
2014-08-04 22:59 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E0062A.8030204@nod.at \
--to=richard@nod.at \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sahne@0x90.at \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.