From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Sat, 4 Jun 2016 11:40:02 +0000 (-0500)
Subject: mount.2: Note the default treatment of ATIME flags during MS_REMOUNT
X-Git-Tag: man-pages-4.07~227
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=49f6854626c40802d5527dad9d7fa29f860306f7;p=thirdparty%2Fman-pages.git

mount.2: Note the default treatment of ATIME flags during MS_REMOUNT

The behavior changed in Linux 3.17.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---

diff --git a/man2/mount.2 b/man2/mount.2
index 34d71cb8a4..a582443bbe 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -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