fallocate.2, fcntl.2, lseek.2, madvise.2, memfd_create.2, mmap.2, remap_file_pages.2, swapon.2, proc.5, cgroups.7, shm_overview.7, user_namespaces.7: Fix cross references to new tmpfs(5) page

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

man2/fallocate.2

@@ -132,7 +132,7 @@ ext4 (since Linux 3.0)
 .IP *
 Btrfs (since Linux 3.7)
 .IP *
-tmpfs (since Linux 3.5)
+.BR tmpfs "(5) (since Linux 3.5)"
 .\" commit 83e4fa9c16e4af7122e31be3eca5d57881d236fe
 .SS Collapsing file space
 .\" commit 00f5e61998dd17f5375d9dfc01331f104b83f841

man2/fcntl.2

@@ -1364,7 +1364,7 @@ and some code examples, see
 .BR memfd_create (2).
 
 Currently, only the
-.I tmpfs
+.BR tmpfs (5)
 filesystem supports sealing.
 On other filesystems, all
 .BR fcntl ()

man2/lseek.2

@@ -175,7 +175,7 @@ XFS (since Linux 3.5)
 .IP *
 ext4 (since Linux 3.8)
 .IP *
-tmpfs (since Linux 3.8)
+.BR tmpfs "(5) (since Linux 3.8)"
 .IP *
 NFS (since Linux 3.18)
 .\" commit 1c6dcbe5ceff81c2cf8d929646af675cd59fe7c0

man2/madvise.2

@@ -184,7 +184,9 @@ This flag cannot be applied to locked pages, Huge TLB pages, or
 .BR VM_PFNMAP
 pages.
 
-In the initial implementation, only shmfs/tmpfs is supported
+In the initial implementation, only
+.BR tmpfs (5)
+is supported
 .BR MADV_REMOVE ;
 but since Linux 3.5,
 .\" commit 3f31d07571eeea18a7d34db9af21d2285b807a17

man2/memfd_create.2

@@ -172,7 +172,7 @@ Glibc does not provide a wrapper for this system call; call it using
 The
 .BR memfd_create ()
 system call provides a simple alternative to manually mounting a
-.I tmpfs
+.BR tmpfs (5)
 filesystem and creating and opening a file in that filesystem.
 The primary purpose of
 .BR memfd_create ()
@@ -221,7 +221,7 @@ its peer can't modify the shared memory in an undesired fashion.
 An example of the usage of the sealing mechanism is as follows:
 .IP 1. 3
 The first process creates a
-.I tmpfs
+.BR tmpfs (5)
 file using
 .BR memfd_create ().
 The call yields a file descriptor used in subsequent steps.
@@ -244,7 +244,7 @@ then it will be necessary to first unmap the shared writable mapping
 created in the previous step.)
 .IP 4.
 A second process obtains a file descriptor for the
-.I tmpfs
+.BR tmpfs (5)
 file and maps it.
 Among the possible ways in which this could happen are the following:
 .RS
@@ -301,7 +301,7 @@ and the file sealing API.
 The first program,
 .IR t_memfd_create.c ,
 creates a
-.I tmpfs
+.BR tmpfs (5)
 file using
 .BR memfd_create (),
 sets a size for the file, maps it into memory,
@@ -321,7 +321,7 @@ and inspect the set of seals that have been applied to that file.
 
 The following shell session demonstrates the use of these programs.
 First we create a
-.I tmpfs
+.BR tmpfs (5)
 file and set some seals on it:
 
 .in +4n

man2/mmap.2

@@ -723,7 +723,8 @@ subsequent mappings may see the modified content.
 In some cases, this could be fixed by calling
 .BR msync (2)
 before the unmap takes place;
-however, this doesn't work on tmpfs
+however, this doesn't work on
+.BR tmpfs (5)
 (for example, when using POSIX shared memory interface documented in
 .BR shm_overview (7)).
 .SH EXAMPLE

man2/remap_file_pages.2

@@ -167,7 +167,9 @@ Since Linux 2.6.23,
 .\" commit 3ee6dafc677a68e461a7ddafc94a580ebab80735
 .BR remap_file_pages ()
 creates non-linear mappings only
-on in-memory file systems such as tmpfs, hugetlbfs or ramfs.
+on in-memory file systems such as
+.BR tmpfs (5),
+hugetlbfs or ramfs.
 On filesystems with a backing store,
 .BR remap_file_pages ()
 is not much more efficient than using

man2/swapon.2

@@ -130,7 +130,8 @@ exists, but refers neither to a regular file nor to a block device;
 .B EINVAL
 .RB ( swapon ())
 The indicated path does not contain a valid swap signature or
-resides on an in-memory filesystem such as tmpfs.
+resides on an in-memory filesystem such as
+.BR tmpfs (5).
 .TP
 .BR EINVAL " (since Linux 3.4)"
 .RB ( swapon ())

man5/proc.5

@@ -2317,7 +2317,9 @@ Size of resident file mappings.
 .IP *
 .IR RssShmem :
 Size of resident shared memory (includes System V shared memory,
-mappings from tmpfs, and shared anonymous mappings).
+mappings from
+.BR tmpfs (5),
+and shared anonymous mappings).
 .\" commit bf9683d6990589390b5178dafe8fd06808869293
 (since Linux 4.5).
 .IP *
@@ -3180,8 +3182,9 @@ Non-file backed huge pages mapped into user-space page tables.
 .TP
 .IR ShmemHugePages " %lu (since Linux 4.8)"
 (\fBCONFIG_TRANSPARENT_HUGEPAGE\fP is required.)
-Memory used by shared memory (shmem) and tmpfs allocated
-with huge pages
+Memory used by shared memory (shmem) and
+.BR tmpfs (5)
+allocated with huge pages
 .TP
 .IR ShmemPmdMapped " %lu (since Linux 4.8)"
 (\fBCONFIG_TRANSPARENT_HUGEPAGE\fP is required.)
@@ -5380,7 +5383,8 @@ Amount of memory allocated to kernel stacks.
 .TP
 .IR nr_shmem " (since Linux 2.6.32)"
 .\" commit 4b02108ac1b3354a22b0d83c684797692efdc395
-Pages used by shmem and tmpfs.
+Pages used by shmem and
+.BR tmpfs (5).
 .TP
 .IR nr_dirtied " (since Linux 2.6.37)"
 .\" commit ea941f0e2a8c02ae876cd73deb4e1557248f258c

man7/cgroups.7

@@ -162,7 +162,9 @@ configuration option that must be set in order to employ that controller.
 
 In order to use a v1 controller,
 it must be mounted against a cgroup filesystem.
-The usual place for such mounts is under a tmpfs filesystem mounted at
+The usual place for such mounts is under a
+.BR tmpfs (5)
+filesystem mounted at
 .IR /sys/fs/cgroup .
 Thus, one might mount the
 .I cpu

man7/shm_overview.7

@@ -93,7 +93,7 @@ to link against the real-time library,
 .IR librt .
 .SS Accessing shared memory objects via the filesystem
 On Linux, shared memory objects are created in a
-.RI ( tmpfs )
+.RI ( tmpfs (5))
 virtual filesystem, normally mounted under
 .IR /dev/shm .
 Since kernel 2.6.19, Linux supports the use of access control lists (ACLs)

man7/user_namespaces.7

@@ -247,7 +247,7 @@ and mount the following types of filesystems:
 .IR devpts
 (since Linux 3.9)
 .IP *
-.IR tmpfs
+.BR tmpfs (5)
 (since Linux 3.9)
 .IP *
 .IR ramfs