From: Andi Kleen <ak@suse.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linuxram@us.ibm.com
Subject: Re: [PATCH 17/18] unbindable mounts
Date: 13 Nov 2005 04:00:18 +0100 [thread overview]
Message-ID: <p73d5l545h9.fsf@verdi.suse.de> (raw)
In-Reply-To: <E1EZInj-0001F9-CG@ZenIV.linux.org.uk>
Al Viro <viro@ftp.linux.org.uk> writes:
> From: Ram Pai <linuxram@us.ibm.com>
> Date: 1131402080 -0500
>
> A unbindable mount does not forward or receive propagation. Also unbindable
> mount disallows bind mounts. The semantics is as follows.
>
> Bind semantics:
> Its invalid to bind mount a unbindable mount.
> Move semantics:
> Its invalid to move a unbindable mount under shared mount.
> Clone-namespace semantics:
> If a mount is unbindable in the parent namespace, the corresponding
> cloned mount in the child namespace becomes unbindable too. Note:
> there is subtle difference, unbindable mounts cannot be bind mounted
> but can be cloned during clone-namespace.
What is it good for?
Normally I would have expected that to be part of the description.
-Andi (slightly worried about all these different mount variants. Hopefully
you guys themselves can still keep them all in your heads)
next prev parent reply other threads:[~2005-11-13 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 2:01 [PATCH 17/18] unbindable mounts Al Viro
2005-11-13 3:00 ` Andi Kleen [this message]
2005-11-14 19:18 ` Ram Pai
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=p73d5l545h9.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=viro@ftp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox