From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH v2 2/2] mount.2: MS_BIND still ignores mountflags
Date: Sat, 21 May 2016 11:29:50 -0500 [thread overview]
Message-ID: <7e6468ec-fd5d-bfdd-c86f-925b3d9fc251@gmail.com> (raw)
In-Reply-To: <b7d41a470056188c253e61095fe40e02cbf03040.1463597825.git.osandov@fb.com>
On 05/18/2016 01:57 PM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> This is clear from the do_mount() function in the kernel as of v4.6.
>
Hello Omar
I've applied this patch, and await your input on the other patch.
Cheers,
Michael
> Signed-off-by: Omar Sandoval <osandov@fb.com>
> ---
> man2/mount.2 | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/man2/mount.2 b/man2/mount.2
> index 419e22da800f..bd4c35bd15ff 100644
> --- a/man2/mount.2
> +++ b/man2/mount.2
> @@ -98,10 +98,10 @@ The
> and
> .IR data
> arguments are ignored.
> -Up until Linux 2.6.26,
> +The
> .I mountflags
> -was also ignored
> -.\" with the exception of the "hidden" MS_REC mountflags bit
> +argument is also ignored, with the exception of
> +.B MS_REC
> (the bind mount has the same mount options as
> the underlying mount point).
> .TP
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-05-21 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 18:57 [PATCH v2 1/2] mount.2: document MS_REC and shared subtree flags Omar Sandoval
2016-05-18 18:57 ` [PATCH v2 2/2] mount.2: MS_BIND still ignores mountflags Omar Sandoval
2016-05-21 16:29 ` Michael Kerrisk (man-pages) [this message]
2016-05-19 11:22 ` [PATCH v2 1/2] mount.2: document MS_REC and shared subtree flags Michael Kerrisk (man-pages)
2016-06-07 18:15 ` Omar Sandoval
2016-06-07 22:40 ` Michael Kerrisk (man-pages)
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=7e6468ec-fd5d-bfdd-c86f-925b3d9fc251@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
/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;
as well as URLs for NNTP newsgroup(s).