From: NeilBrown <neilb@suse.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] mount.2: revise description of MS_REMOUNT | MS_BIND
Date: Fri, 19 May 2017 16:55:34 +1000 [thread overview]
Message-ID: <87zie9jpy1.fsf@notabene.neil.brown.name> (raw)
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
MS_REMOUNT|MS_BIND affect all per-mount-point
flag. MS_READONLY is only special because it,
uniquely, is both a per-mount-point flag *and* a
per-filesystem flag.
So the sections of per-mount-point flags and
MS_REMOUNT can usefully be clarified.
Signed-off-by: NeilBrown <neilb@suse.com>
---
man2/mount.2 | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/man2/mount.2 b/man2/mount.2
index 35fdda084d61..3e5348368757 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -288,6 +288,12 @@ are also settable on a per-mount-point basis.
The
.B MS_RELATIME
flag is also settable on a per-mount-point basis.
+Since Linux 2.6.16,
+.B MS_RDONLY
+can be set or cleared on a per-mount-point basis as well as on
+the underlying filesystem. The mounted filesystem will only be
+writable if neither the filesystem nor the mountpoint are flagged as
+read-only.
.\"
.SS Remounting an existing mount
An existing mount may be remounted by specifying
@@ -317,6 +323,10 @@ and
arguments should match the values used in the original
.BR mount ()
call, except for those parameters that are being deliberately changed.
+Another exception is that
+.B MS_BIND
+has a different meaning for remount, and it should only be included if
+explicitly desired.
The following
.I mountflags
@@ -351,17 +361,20 @@ then the remount operation preserves the existing values of these flags
(rather than defaulting to
.BR MS_RELATIME ).
-Since Linux 2.6.26, this flag can also be used to make
+Since Linux 2.6.26, this flag can be used with
+.B MS_BIND
+to only modify the per-mount-point flags.
.\" See https://lwn.net/Articles/281157/
-an existing bind mount read-only by specifying
+This is particularly useful for setting or clearing the "read-only"
+flag on a mount point without changing the underlying filesystem.
+Specifying
.IR mountflags
as:
MS_REMOUNT | MS_BIND | MS_RDONLY
-Note that only the
-.BR MS_RDONLY
-setting of the bind mount can be changed in this manner.
+will make access through this mountpoint read-only, without affecting
+other mount points.
.\"
.SS Creating a bind mount
If
--
2.12.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2017-05-19 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 6:55 NeilBrown [this message]
2017-05-22 11:43 ` [PATCH] mount.2: revise description of MS_REMOUNT | MS_BIND 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=87zie9jpy1.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).