msync.2: s/flushes... back to disk/flushes... back to filesystem/

As noted by Heinrich:

    The manpage of msync(2) says:
        "msync() flushes changes made to the in-core copy of a file
        that was mapped into memory using mmap(2) back to disk."
    ...
    "back to disk" implies that the file system is forced to
    actually write to the hard disk, somewhat equivalent to
    invoking sync(1).  Is that guaranteed for all file systems?

    Not all file systems are necessarily disk based
    (e.g. davfs, tmpfs).

    So shouldn't we write:
        "... back to the file system."

    http://pubs.opengroup.org/onlinepubs/007904875/functions/msync.html
    says "... to permanent storage locations, if any,"

Reported-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/man2/msync.2 b/man2/msync.2
index 6ba64fa8c..baf7df9dc 100644
--- a/man2/msync.2
+++ b/man2/msync.2
@@ -34,7 +34,7 @@ msync \- synchronize a file with a memory map
 flushes changes made to the in-core copy of a file that was mapped
 into memory using
 .BR mmap (2)
-back to disk.
+back to the filesystem.
 Without use of this call
 there is no guarantee that changes are written back before
 .BR munmap (2)