]> git.ipfire.org Git - thirdparty/man-pages.git/commitdiff
mount.2: Note the default treatment of ATIME flags during MS_REMOUNT
authorMichael Kerrisk <mtk.manpages@gmail.com>
Sat, 4 Jun 2016 11:40:02 +0000 (06:40 -0500)
committerMichael Kerrisk <mtk.manpages@gmail.com>
Sat, 4 Jun 2016 11:57:44 +0000 (06:57 -0500)
The behavior changed in Linux 3.17.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
man2/mount.2

index 34d71cb8a4ce2ef12ff83c80fe6cda8e733e563a..a582443bbe30b047275e4fa620f52102de63960a 100644 (file)
@@ -314,6 +314,20 @@ and, additionally, before kernel 2.4.10, the following could also be changed:
 and
 .BR MS_NOEXEC .
 
+Since Linux 3.17,
+.\" commit ffbc6f0ead47fa5a1dc9642b0331cb75c20a640e
+if none of
+.BR MS_NOATIME ,
+.BR MS_NODIRATIME ,
+.BR MS_RELATIME ,
+or
+.BR MS_STRICTATIME
+is specified in
+.IR mountflags ,
+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
 .\" See https://lwn.net/Articles/281157/
 an existing bind mount read-only by specifying