Also remove quotation marks around a single argument (mmap.2). The output from "nroff" and "groff" is unchanged, except a font change for a punctuation mark (mlock.2, mprotect.2) Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/madvise.2 | 44 +++++++++--------- man2/mbind.2 | 4 +- man2/membarrier.2 | 12 ++--- man2/memfd_create.2 | 28 +++++------ man2/migrate_pages.2 | 2 +- man2/mkdir.2 | 4 +- man2/mlock.2 | 6 +-- man2/mmap.2 | 40 ++++++++-------- man2/modify_ldt.2 | 4 +- man2/mount.2 | 108 +++++++++++++++++++++---------------------- man2/mprotect.2 | 26 +++++------ man2/mremap.2 | 2 +- man2/msgctl.2 | 4 +- man2/msgget.2 | 2 +- man2/msgop.2 | 12 ++--- man2/msync.2 | 12 ++--- 16 files changed, 155 insertions(+), 155 deletions(-) diff --git a/man2/madvise.2 b/man2/madvise.2 index 5367633d1..4c5c20e1e 100644 --- a/man2/madvise.2 +++ b/man2/madvise.2 @@ -75,7 +75,7 @@ values, which are also available on several other implementations. .BR madvise () is not specified in POSIX.) Subsequently, a number of Linux-specific -.IR advice +.I advice values have been added. .\" .\" ====================================================================== @@ -138,7 +138,7 @@ and shmem-based techniques such as System V shared memory segments) or zero-fill-on-demand pages for anonymous private mappings. .IP Note that, when applied to shared mappings, -.BR MADV_DONTNEED +.B MADV_DONTNEED might not lead to immediate freeing of the pages in the range. The kernel is free to delay freeing the pages until an appropriate moment. The resident set size (RSS) of the calling process will be immediately @@ -146,7 +146,7 @@ reduced however. .IP .B MADV_DONTNEED cannot be applied to locked pages, Huge TLB pages, or -.BR VM_PFNMAP +.B VM_PFNMAP pages. (Pages marked with the kernel-internal .B VM_PFNMAP @@ -184,7 +184,7 @@ bytes containing zero. .IP The specified address range must be mapped shared and writable. This flag cannot be applied to locked pages, Huge TLB pages, or -.BR VM_PFNMAP +.B VM_PFNMAP pages. .IP In the initial implementation, only @@ -195,11 +195,11 @@ but since Linux 3.5, .\" commit 3f31d07571eeea18a7d34db9af21d2285b807a17 any filesystem which supports the .BR fallocate (2) -.BR FALLOC_FL_PUNCH_HOLE +.B FALLOC_FL_PUNCH_HOLE mode also supports .BR MADV_REMOVE . Hugetlbfs fails with the error -.BR EINVAL +.B EINVAL and other filesystems fail with the error .BR EOPNOTSUPP . .TP @@ -246,7 +246,7 @@ restoring the default behavior, whereby a mapping is inherited across Poison the pages in the range specified by .I addr and -.IR length +.I length and handle subsequent references to those pages like a hardware memory corruption. This operation is available only for privileged @@ -282,18 +282,18 @@ See the Linux kernel source file for more details. .IP The -.BR MADV_MERGEABLE +.B MADV_MERGEABLE and -.BR MADV_UNMERGEABLE +.B MADV_UNMERGEABLE operations are available only if the kernel was configured with .BR CONFIG_KSM . .TP .BR MADV_UNMERGEABLE " (since Linux 2.6.32)" Undo the effect of an earlier -.BR MADV_MERGEABLE +.B MADV_MERGEABLE operation on the specified address range; KSM unmerges whatever pages it had merged in the address range specified by -.IR addr +.I addr and .IR length . .TP @@ -343,17 +343,17 @@ See the Linux kernel source file for more details. .IP The -.BR MADV_HUGEPAGE +.B MADV_HUGEPAGE and -.BR MADV_NOHUGEPAGE +.B MADV_NOHUGEPAGE operations are available only if the kernel was configured with .BR CONFIG_TRANSPARENT_HUGEPAGE . .TP .BR MADV_NOHUGEPAGE " (since Linux 2.6.38)" Ensures that memory in the address range specified by -.IR addr +.I addr and -.IR length +.I length will not be collapsed into huge pages. .TP .BR MADV_DONTDUMP " (since Linux 3.4)" @@ -366,7 +366,7 @@ and This is useful in applications that have large areas of memory that are known not to be useful in a core dump. The effect of -.BR MADV_DONTDUMP +.B MADV_DONTDUMP takes precedence over the bit mask that is set via the .I /proc/[pid]/coredump_filter file (see @@ -378,7 +378,7 @@ Undo the effect of an earlier .TP .BR MADV_FREE " (since Linux 4.5)" The application no longer requires the pages in the range specified by -.IR addr +.I addr and .IR len . The kernel can thus free these pages, @@ -473,7 +473,7 @@ is not a valid. is .B MADV_DONTNEED or -.BR MADV_REMOVE +.B MADV_REMOVE and the specified address range includes locked, Huge TLB pages, or .B VM_PFNMAP pages. @@ -481,7 +481,7 @@ pages. .B EINVAL .I advice is -.BR MADV_MERGEABLE +.B MADV_MERGEABLE or .BR MADV_UNMERGEABLE , but the kernel was not configured with @@ -490,13 +490,13 @@ but the kernel was not configured with .B EINVAL .I advice is -.BR MADV_FREE +.B MADV_FREE or -.BR MADV_WIPEONFORK +.B MADV_WIPEONFORK but the specified address range includes file, Huge TLB, .BR MAP_SHARED , or -.BR VM_PFNMAP +.B VM_PFNMAP ranges. .TP .B EIO diff --git a/man2/mbind.2 b/man2/mbind.2 index 16644ff6a..c6d08c83e 100644 --- a/man2/mbind.2 +++ b/man2/mbind.2 @@ -122,7 +122,7 @@ argument must specify one of .BR MPOL_INTERLEAVE , .BR MPOL_PREFERRED , or -.BR MPOL_LOCAL +.B MPOL_LOCAL (which are described in detail below). All policy modes except .B MPOL_DEFAULT @@ -343,7 +343,7 @@ and .I maxnode points outside your accessible address space. Or, there was an unmapped hole in the specified memory range specified by -.IR addr +.I addr and .IR len . .TP diff --git a/man2/membarrier.2 b/man2/membarrier.2 index 41d7a303a..71a785a73 100644 --- a/man2/membarrier.2 +++ b/man2/membarrier.2 @@ -107,7 +107,7 @@ previously registered with .IP Given that registration is about the intent to receive the barriers, it is valid to invoke -.BR MEMBARRIER_CMD_GLOBAL_EXPEDITED +.B MEMBARRIER_CMD_GLOBAL_EXPEDITED from a process that has not employed .BR MEMBARRIER_CMD_REGISTER_GLOBAL_EXPEDITED . .IP @@ -116,7 +116,7 @@ they never block, but have the downside of causing extra overhead. .TP .BR MEMBARRIER_CMD_REGISTER_GLOBAL_EXPEDITED " (since Linux 4.16)" Register the process's intent to receive -.BR MEMBARRIER_CMD_GLOBAL_EXPEDITED +.B MEMBARRIER_CMD_GLOBAL_EXPEDITED memory barriers. .TP .BR MEMBARRIER_CMD_PRIVATE_EXPEDITED " (since Linux 4.14)" @@ -161,7 +161,7 @@ Register the process's intent to use .TP .BR MEMBARRIER_CMD_SHARED " (since Linux 4.3)" This is an alias for -.BR MEMBARRIER_CMD_GLOBAL +.B MEMBARRIER_CMD_GLOBAL that exists for header backward compatibility. .PP The @@ -224,13 +224,13 @@ set to 0, error handling is required only for the first call to is invalid, or .I flags is nonzero, or the -.BR MEMBARRIER_CMD_GLOBAL +.B MEMBARRIER_CMD_GLOBAL command is disabled because the .I nohz_full CPU parameter has been set, or the -.BR MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE +.B MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE and -.BR MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_SYNC_CORE +.B MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_SYNC_CORE commands are not implemented by the architecture. .TP .B ENOSYS diff --git a/man2/memfd_create.2 b/man2/memfd_create.2 index 3cd392d1b..05a9ce87a 100644 --- a/man2/memfd_create.2 +++ b/man2/memfd_create.2 @@ -48,7 +48,7 @@ have the same semantics as other anonymous memory allocations such as those allocated using .BR mmap (2) with the -.BR MAP_ANONYMOUS +.B MAP_ANONYMOUS flag. .PP The initial size of the file is set to 0. @@ -64,17 +64,17 @@ is used as a filename and will be displayed as the target of the corresponding symbolic link in the directory .IR /proc/self/fd/ . The displayed name is always prefixed with -.IR memfd: +.I memfd: and serves only for debugging purposes. Names do not affect the behavior of the file descriptor, and as such multiple files can have the same name without any side effects. .PP The following values may be bitwise ORed in -.IR flags +.I flags to change the behavior of .BR memfd_create (): .TP -.BR MFD_CLOEXEC +.B MFD_CLOEXEC Set the close-on-exec .RB ( FD_CLOEXEC ) flag on the new file descriptor. @@ -84,12 +84,12 @@ flag in .BR open (2) for reasons why this may be useful. .TP -.BR MFD_ALLOW_SEALING +.B MFD_ALLOW_SEALING Allow sealing operations on this file. See the discussion of the .B F_ADD_SEALS and -.BR F_GET_SEALS +.B F_GET_SEALS operations in .BR fcntl (2), and also NOTES, below. @@ -165,7 +165,7 @@ is set to indicate the error. .TP .B EFAULT The address in -.IR name +.I name points to invalid memory. .TP .B EINVAL @@ -223,10 +223,10 @@ The .BR memfd_create () system call also has uses without file sealing (which is why file-sealing is disabled, unless explicitly requested with the -.BR MFD_ALLOW_SEALING +.B MFD_ALLOW_SEALING flag). In particular, it can be used as an alternative to creating files in -.IR tmp +.I tmp or as an alternative to using the .BR open (2) .B O_TMPFILE @@ -244,11 +244,11 @@ time-of-check-to-time-of-use race conditions (typically dealt with by copying data from the shared memory region before checking and using it). The latter possibility leaves the local process vulnerable to -.BR SIGBUS +.B SIGBUS signals when an attempt is made to access a now-nonexistent location in the shared memory region. (Dealing with this possibility necessitates the use of a handler for the -.BR SIGBUS +.B SIGBUS signal.) .PP Dealing with untrusted peers imposes extra complexity on @@ -330,7 +330,7 @@ This bit mask can be inspected in order to determine what kinds of restrictions have been placed on file modifications. If desired, the second process can apply further seals to impose additional restrictions (so long as the -.BR F_SEAL_SEAL +.B F_SEAL_SEAL seal has not yet been applied). .SH EXAMPLE Below are shown two example programs that demonstrate the use of @@ -378,11 +378,11 @@ From another program, we can obtain a file descriptor for the file created by .BR memfd_create () by opening the -.IR /proc/[pid]/fd +.I /proc/[pid]/fd file that corresponds to the file descriptor opened by .BR memfd_create (). Using that pathname, we inspect the content of the -.IR /proc/[pid]/fd +.I /proc/[pid]/fd symbolic link, and use our .I t_get_seals program to view the seals that have been placed on the file: diff --git a/man2/migrate_pages.2 b/man2/migrate_pages.2 index d3effc234..5b74d786f 100644 --- a/man2/migrate_pages.2 +++ b/man2/migrate_pages.2 @@ -180,5 +180,5 @@ or a similar package. .BR migratepages (8), .BR numastat (8) .PP -.IR Documentation/vm/page_migration.rst +.I Documentation/vm/page_migration.rst in the Linux kernel source tree diff --git a/man2/mkdir.2 b/man2/mkdir.2 index 12b131270..ca23028dd 100644 --- a/man2/mkdir.2 +++ b/man2/mkdir.2 @@ -235,9 +235,9 @@ When .I pathname is a relative pathname, glibc constructs a pathname based on the symbolic link in -.IR /proc/self/fd +.I /proc/self/fd that corresponds to the -.IR dirfd +.I dirfd argument. .SH SEE ALSO .BR mkdir (1), diff --git a/man2/mlock.2 b/man2/mlock.2 index f3f3c8abd..9adb151e2 100644 --- a/man2/mlock.2 +++ b/man2/mlock.2 @@ -222,7 +222,7 @@ Some or all of the specified address range could not be locked. The result of the addition .IR addr + len was less than -.IR addr +.I addr (e.g., the addition may have resulted in an overflow). .TP .B EINVAL @@ -455,11 +455,11 @@ then the already locked bytes in the overlapping region were counted twice when checking against the limit. Such double accounting could incorrectly calculate a "total locked memory" value for the process that exceeded the -.BR RLIMIT_MEMLOCK +.B RLIMIT_MEMLOCK limit, with the result that .BR mlock () and -.BR mlock2() +.BR mlock2 () would fail on requests that should have succeeded. This bug was fixed .\" commit 0cf2f6f6dc605e587d2c1120f295934c77e810e8 diff --git a/man2/mmap.2 b/man2/mmap.2 index fccfb9b3e..65262c67d 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -143,7 +143,7 @@ By contrast, when creating a mapping using .BR MAP_SHARED_VALIDATE , the kernel verifies all passed flags are known and fails the mapping with the error -.BR EOPNOTSUPP +.B EOPNOTSUPP for unknown flags. This mapping type is also required to be able to use some mapping flags (e.g., @@ -256,12 +256,12 @@ If the specified address cannot be used, will fail. .IP Software that aspires to be portable should use the -.BR MAP_FIXED +.B MAP_FIXED flag with care, keeping in mind that the exact layout of a process's memory mappings is allowed to change significantly between kernel versions, C library versions, and operating system releases. -.IR "Carefully read the discussion of this flag in NOTES!" +.I Carefully read the discussion of this flag in NOTES! .TP .BR MAP_FIXED_NOREPLACE " (since Linux 4.17)" .\" commit a4ff8e8620d3f4f50ac4b41e8067b7d395056843 @@ -280,7 +280,7 @@ This flag can therefore be used as a way to atomically one thread will succeed; all others will report failure. .IP Note that older kernels which do not recognize the -.BR MAP_FIXED_NOREPLACE +.B MAP_FIXED_NOREPLACE flag will typically (upon detecting a collision with a preexisting mapping) fall back to a "non-\c .B MAP_FIXED\c @@ -354,7 +354,7 @@ plus .BR mlock (2) when major faults are not acceptable after the initialization of the mapping. The -.BR MAP_LOCKED +.B MAP_LOCKED flag is ignored in older kernels. .\" If set, the mapped pages will not be swapped out. .TP @@ -365,12 +365,12 @@ Don't perform read-ahead: create page tables entries only for pages that are already present in RAM. Since Linux 2.6.23, this flag causes -.BR MAP_POPULATE +.B MAP_POPULATE to do nothing. One day, the combination of -.BR MAP_POPULATE +.B MAP_POPULATE and -.BR MAP_NONBLOCK +.B MAP_NONBLOCK may be reimplemented. .TP .B MAP_NORESERVE @@ -392,7 +392,7 @@ private writable mappings. Populate (prefault) page tables for a mapping. For a file mapping, this causes read-ahead on the file. This will help to reduce blocking on page faults later. -.BR MAP_POPULATE +.B MAP_POPULATE is supported for private mappings only since Linux 2.6.23. .TP .BR MAP_STACK " (since Linux 2.6.27)" @@ -536,13 +536,13 @@ is not a valid file descriptor (and was not set). .TP .B EEXIST -.BR MAP_FIXED_NOREPLACE +.B MAP_FIXED_NOREPLACE was specified in .IR flags , and the range covered by -.IR addr +.I addr and -.IR length +.I length clashes with an existing mapping. .TP .B EINVAL @@ -701,15 +701,15 @@ Certain .I flags constants are defined only if suitable feature test macros are defined (possibly by default): -.BR _DEFAULT_SOURCE +.B _DEFAULT_SOURCE with glibc 2.19 or later; or -.BR _BSD_SOURCE +.B _BSD_SOURCE or -.BR _SVID_SOURCE +.B _SVID_SOURCE in glibc 2.19 and earlier. (Employing -.BR _GNU_SOURCE +.B _GNU_SOURCE also suffices, and requiring that macro specifically would have been more logical, since these flags are all Linux-specific.) @@ -736,14 +736,14 @@ currently resident in the buffer/page cache using .\" .SS Using MAP_FIXED safely The only safe use for -.BR MAP_FIXED +.B MAP_FIXED is where the address range specified by -.IR addr +.I addr and .I length was previously reserved using another mapping; otherwise, the use of -.BR MAP_FIXED +.B MAP_FIXED is hazardous because it forcibly removes preexisting mappings, making it easy for a multithreaded process to corrupt its own address space. .PP @@ -776,7 +776,7 @@ and the PAM libraries .UE . .PP Since Linux 4.17, a multithreaded program can use the -.BR MAP_FIXED_NOREPLACE +.B MAP_FIXED_NOREPLACE flag to avoid the hazard described above when attempting to create a mapping at a fixed address that has not been reserved by a preexisting mapping. diff --git a/man2/modify_ldt.2 b/man2/modify_ldt.2 index 0db6efea4..6f5907440 100644 --- a/man2/modify_ldt.2 +++ b/man2/modify_ldt.2 @@ -192,14 +192,14 @@ Even on 64-bit kernels, .BR modify_ldt () cannot be used to create a long mode (i.e., 64-bit) code segment. The undocumented field "lm" in -.IR user_desc +.I user_desc is not useful, and, despite its name, does not result in a long mode segment. .SH BUGS On 64-bit kernels before Linux 3.19, .\" commit e30ab185c490e9a9381385529e0fd32f0a399495 setting the "lm" bit in -.IR user_desc +.I user_desc prevents the descriptor from being considered empty. Keep in mind that the "lm" bit does not exist in the 32-bit headers, but these buggy kernels diff --git a/man2/mount.2 b/man2/mount.2 index 8f6dcf8a1..2352d7c89 100644 --- a/man2/mount.2 +++ b/man2/mount.2 @@ -91,17 +91,17 @@ testing the bits set in with the tests being conducted in the order listed here: .IP * 3 Remount an existing mount: -.IR mountflags +.I mountflags includes .BR MS_REMOUNT . .IP * Create a bind mount: -.IR mountflags +.I mountflags includes .BR MS_BIND . .IP * Change the propagation type of an existing mount: -.IR mountflags +.I mountflags includes one of .BR MS_SHARED , .BR MS_PRIVATE , @@ -110,17 +110,17 @@ or .BR MS_UNBINDABLE . .IP * Move an existing mount to a new location: -.IR mountflags +.I mountflags includes .BR MS_MOVE . .IP * Create a new mount: -.IR mountflags +.I mountflags includes none of the above flags. .PP Each of these operations is detailed later in this page. Further flags may be specified in -.IR mountflags +.I mountflags to modify the behavior of .BR mount (), as described below. @@ -175,9 +175,9 @@ as well as cases where the .B MS_STRICTATIME mount option is also enabled. (The advantage of combining -.BR MS_STRICTATIME +.B MS_STRICTATIME and -.BR MS_LAZYTIME +.B MS_LAZYTIME is that .BR stat (2) will return the correctly updated atime, but the atime updates @@ -207,7 +207,7 @@ Do not update access times for directories on this filesystem. This flag provides a subset of the functionality provided by .BR MS_NOATIME ; that is, -.BR MS_NOATIME +.B MS_NOATIME implies .BR MS_NODIRATIME . .TP @@ -228,7 +228,7 @@ Mount filesystem read-only. .TP .BR MS_REC " (since Linux 2.4.11)" Used in conjunction with -.BR MS_BIND +.B MS_BIND to create a recursive bind mount, and in conjunction with the propagation type flags to recursively change the propagation type of all of the mounts in a subtree. @@ -244,7 +244,7 @@ This option is useful for programs, such as that need to know when a file has been read since it was last modified. Since Linux 2.6.30, the kernel defaults to the behavior provided by this flag (unless -.BR MS_NOATIME +.B MS_NOATIME was specified), and the .B MS_STRICTATIME flag is required to obtain traditional semantics. @@ -260,7 +260,7 @@ Suppress the display of certain .RI ( printk ()) warning messages in the kernel log. This flag supersedes the misnamed and obsolete -.BR MS_VERBOSE +.B MS_VERBOSE flag (available since Linux 2.4.12), which has the same meaning. .TP .BR MS_STRICTATIME " (since Linux 2.6.30)" @@ -268,9 +268,9 @@ Always update the last access time (atime) when files on this filesystem are accessed. (This was the default behavior before Linux 2.6.30.) Specifying this flag overrides the effect of setting the -.BR MS_NOATIME +.B MS_NOATIME and -.BR MS_RELATIME +.B MS_RELATIME flags. .TP .B MS_SYNCHRONOUS @@ -374,11 +374,11 @@ can be changed: .BR MS_NOSUID , .BR MS_RELATIME , .BR MS_RDONLY , -.BR MS_STRICTATIME +.B MS_STRICTATIME (whose effect is to clear the -.BR MS_NOATIME +.B MS_NOATIME and -.BR MS_RELATIME +.B MS_RELATIME flags), and .BR MS_SYNCHRONOUS . @@ -387,9 +387,9 @@ Attempts to change the setting of the .\" which excludes MS_DIRSYNC and MS_SILENT, although SB_DIRSYNC .\" and SB_SILENT are split out as per-superblock flags in do_mount() .\" (Linux 4.17 source code) -.BR MS_DIRSYNC +.B MS_DIRSYNC and -.BR MS_SILENT +.B MS_SILENT flags during a remount are silently ignored. Note that changes to per-superblock flags are visible via all mount points of the associated filesystem @@ -402,7 +402,7 @@ if none of .BR MS_NODIRATIME , .BR MS_RELATIME , or -.BR MS_STRICTATIME +.B MS_STRICTATIME is specified in .IR mountflags , then the remount operation preserves the existing values of these flags @@ -418,7 +418,7 @@ to modify only the per-mount-point flags. This is particularly useful for setting or clearing the "read-only" flag on a mount point without changing the underlying filesystem. Specifying -.IR mountflags +.I mountflags as: .PP .in +4n @@ -434,7 +434,7 @@ other mount points. If .I mountflags includes -.BR MS_BIND +.B MS_BIND (available since Linux 2.4), .\" since 2.4.0-test9 then perform a bind mount. @@ -445,9 +445,9 @@ Bind mounts may cross filesystem boundaries and span jails. .PP The -.IR filesystemtype +.I filesystemtype and -.IR data +.I data arguments are ignored. .PP The remaining bits (other than @@ -465,7 +465,7 @@ only that directory is mounted; if there are any submounts under the directory tree, they are not bind mounted. If the -.BR MS_REC +.B MS_REC flag is also specified, then a recursive bind mount operation is performed: all submounts under the .I source @@ -476,34 +476,34 @@ subtree. .\" .SS Changing the propagation type of an existing mount If -.IR mountflags +.I mountflags includes one of .BR MS_SHARED , .BR MS_PRIVATE , .BR MS_SLAVE , or -.BR MS_UNBINDABLE +.B MS_UNBINDABLE (all available since Linux 2.6.15), then the propagation type of an existing mount is changed. If more than one of these flags is specified, an error results. .PP The only other flags that can be specified while changing the propagation type are -.BR MS_REC +.B MS_REC (described below) and -.BR MS_SILENT +.B MS_SILENT (which is ignored). .PP The .IR source , .IR filesystemtype , and -.IR data +.I data arguments are ignored. .PP The meanings of the propagation type flags are as follows: .TP -.BR MS_SHARED +.B MS_SHARED Make this mount point shared. Mount and unmount events immediately under this mount point will propagate to the other mount points that are members of this mount's peer group. @@ -512,11 +512,11 @@ occur under all of the other mount points in the peer group. Conversely, mount and unmount events that take place under peer mount points will propagate to this mount point. .TP -.BR MS_PRIVATE +.B MS_PRIVATE Make this mount point private. Mount and unmount events do not propagate into or out of this mount point. .TP -.BR MS_SLAVE +.B MS_SLAVE If this is a shared mount point that is a member of a peer group that contains other members, convert it to a slave mount. If this is a shared mount point that is a member of a peer group @@ -532,16 +532,16 @@ A mount point can be the slave of another peer group while at the same time sharing mount and unmount events with a peer group of which it is a member. .TP -.BR MS_UNBINDABLE +.B MS_UNBINDABLE Make this mount unbindable. This is like a private mount, and in addition this mount can't be bind mounted. When a recursive bind mount .RB ( mount () with the -.BR MS_BIND +.B MS_BIND and -.BR MS_REC +.B MS_REC flags) is performed on a directory subtree, any unbindable mounts within the subtree are automatically pruned (i.e., not replicated) @@ -555,7 +555,7 @@ If the flag is also specified in .IR mountflags , then the propagation type of all mount points under -.IR target +.I target is also changed. .PP For further details regarding mount propagation types @@ -566,7 +566,7 @@ For further details regarding mount propagation types If .I mountflags contains the flag -.BR MS_MOVE +.B MS_MOVE (available since Linux 2.4.18), then move a subtree: .I source @@ -576,11 +576,11 @@ specifies the new location to which that mount point is to be relocated. The move is atomic: at no point is the subtree unmounted. .PP The remaining bits in the -.IR mountflags +.I mountflags argument are ignored, as are the -.IR filesystemtype +.I filesystemtype and -.IR data +.I data arguments. .\" .SS Creating a new mount point @@ -592,15 +592,15 @@ If none of .BR MS_PRIVATE , .BR MS_SLAVE , or -.BR MS_UNBINDABLE +.B MS_UNBINDABLE is specified in .IR mountflags , then .BR mount () performs its default action: creating a new mount point. -.IR source +.I source specifies the source for the new mount point, and -.IR target +.I target specifies the directory at which to create the mount point. .PP The @@ -608,7 +608,7 @@ The and .I data arguments are employed, and further bits may be specified in -.IR mountflags +.I mountflags to modify the behavior of the call. .\" .SH RETURN VALUE @@ -643,7 +643,7 @@ so that it was marked read-only and can't be remounted as read-write (until the errors are fixed). .IP Some filesystems instead return the error -.BR EROFS +.B EROFS on an attempt to mount a read-only filesystem. .TP .B EACCES @@ -706,16 +706,16 @@ includes .BR MS_PRIVATE , .BR MS_SLAVE , or -.BR MS_UNBINDABLE +.B MS_UNBINDABLE and also includes a flag other than -.BR MS_REC +.B MS_REC or .BR MS_SILENT . .TP -.BR EINVAL +.B EINVAL An attempt was made to bind mount an unbindable mount. .TP -.BR EINVAL +.B EINVAL In an unprivileged mount namespace (i.e., a mount namespace owned by a user namespace that was created by an unprivileged user), @@ -789,7 +789,7 @@ The definitions of .BR MS_SLAVE , .BR MS_STRICTATIME , and -.BR MS_UNBINDABLE +.B MS_UNBINDABLE were added to glibc headers in version 2.12. .\" .SH CONFORMING TO @@ -809,7 +809,7 @@ in the top 16 bits. occupy the low order 16 bits of .IR mountflags .) Specifying -.BR MS_MGC_VAL +.B MS_MGC_VAL was required in kernel versions prior to 2.4, but since Linux 2.4 is no longer required and is ignored if specified. .PP @@ -852,7 +852,7 @@ the mount namespace is preserved across an A process can obtain a private mount namespace if: it was created using the .BR clone (2) -.BR CLONE_NEWNS +.B CLONE_NEWNS flag, in which case its new namespace is initialized to be a .I copy @@ -861,7 +861,7 @@ of the namespace of the process that called or it calls .BR unshare (2) with the -.BR CLONE_NEWNS +.B CLONE_NEWNS flag, which causes the caller's mount namespace to obtain a private copy of the namespace that it was previously sharing with other processes, diff --git a/man2/mprotect.2 b/man2/mprotect.2 index 10e32a4d1..a36afdbdb 100644 --- a/man2/mprotect.2 +++ b/man2/mprotect.2 @@ -118,7 +118,7 @@ Like .BR mprotect (), .BR pkey_mprotect () changes the protection on the pages specified by -.IR addr +.I addr and .IR len . The @@ -156,24 +156,24 @@ to mark it \fIaddr\fP is not a valid pointer, or not a multiple of the system page size. .TP -.BR EINVAL +.B EINVAL .RB ( pkey_mprotect ()) \fIpkey\fP has not been allocated with .BR pkey_alloc (2) .TP -.BR EINVAL +.B EINVAL Both -.BR PROT_GROWSUP +.B PROT_GROWSUP and -.BR PROT_GROWSDOWN +.B PROT_GROWSDOWN were specified in .IR prot . .TP -.BR EINVAL +.B EINVAL Invalid flags specified in .IR prot . .TP -.BR EINVAL +.B EINVAL (PowerPC architecture) .B PROT_SAO was specified in @@ -190,7 +190,7 @@ Addresses in the range are invalid for the address space of the process, or specify one or more pages that are not mapped. (Before kernel 2.4.19, the error -.BR EFAULT +.B EFAULT was incorrectly produced for these cases.) .TP .B ENOMEM @@ -199,9 +199,9 @@ mappings with distinct attributes (e.g., read versus read/write protection) exceeding the allowed maximum. .\" I.e., the number of VMAs would exceed the 64 kB maximum (For example, making the protection of a range -.BR PROT_READ +.B PROT_READ in the middle of a region currently protected as -.BR PROT_READ|PROT_WRITE +.B PROT_READ|PROT_WRITE would result in three mappings: two read/write mappings at each end and a read-only mapping in the middle.) .SH VERSIONS @@ -241,7 +241,7 @@ is set in the process's personality flags (see specifying .B PROT_READ will implicitly add -.BR PROT_EXEC. +.BR PROT_EXEC . .PP On some hardware architectures (e.g., i386), .B PROT_WRITE @@ -264,7 +264,7 @@ and On x86, when .BR mprotect () is used with -.IR prot +.I prot set to .B PROT_EXEC a pkey is may be allocated and set on the memory implicitly @@ -273,7 +273,7 @@ by the kernel, but only when the pkey was 0 previously. On systems that do not support protection keys in hardware, .BR pkey_mprotect () may still be used, but -.IR pkey +.I pkey must be set to 0. When called this way, the operation of .BR pkey_mprotect () diff --git a/man2/mremap.2 b/man2/mremap.2 index 45212e2b0..dd3ef4e1b 100644 --- a/man2/mremap.2 +++ b/man2/mremap.2 @@ -204,7 +204,7 @@ was specified without also specifying shareable mapping (but see BUGS); .IP * \fIold_size\fP was zero and the -.BR MREMAP_MAYMOVE +.B MREMAP_MAYMOVE flag was not specified. .RE .TP diff --git a/man2/msgctl.2 b/man2/msgctl.2 index 2c29ea508..226431be6 100644 --- a/man2/msgctl.2 +++ b/man2/msgctl.2 @@ -236,9 +236,9 @@ structure as for However, .I msg_perm.mode is not checked for read access for -.IR msqid +.I msqid meaning that any user can employ this operation (just as any user may read -.IR /proc/sysvipc/msg +.I /proc/sysvipc/msg to obtain the same information). .SH RETURN VALUE On success, diff --git a/man2/msgget.2 b/man2/msgget.2 index 302ad8efb..4196d5fd1 100644 --- a/man2/msgget.2 +++ b/man2/msgget.2 @@ -165,7 +165,7 @@ capability in the user namespace that governs its IPC namespace. .B EEXIST .B IPC_CREAT and -.BR IPC_EXCL +.B IPC_EXCL were specified in .IR msgflg , but a message queue already exists for diff --git a/man2/msgop.2 b/man2/msgop.2 index d89c49bb2..c480653b2 100644 --- a/man2/msgop.2 +++ b/man2/msgop.2 @@ -211,7 +211,7 @@ set to Unless .B MSG_COPY is specified in -.IR msgflg +.I msgflg (see below), the .I msgtyp @@ -271,14 +271,14 @@ the call fails immediately with the error Because they alter the meaning of .I msgtyp in orthogonal ways, -.BR MSG_COPY +.B MSG_COPY and -.BR MSG_EXCEPT +.B MSG_EXCEPT may not both be specified in .IR msgflg . .IP The -.BR MSG_COPY +.B MSG_COPY flag was added for the implementation of the kernel checkpoint-restore facility and is available only if the kernel was built with the @@ -445,7 +445,7 @@ but not .BR EINVAL " (since Linux 3.14)" .I msgflg specified both -.BR MSG_COPY +.B MSG_COPY and .BR MSG_EXCEPT . .TP @@ -539,7 +539,7 @@ In Linux 3.13 and earlier, if .BR msgrcv () was called with the -.BR MSG_COPY +.B MSG_COPY flag, but without .BR IPC_NOWAIT , and the message queue contained less than diff --git a/man2/msync.2 b/man2/msync.2 index ae8ffba53..7639e9588 100644 --- a/man2/msync.2 +++ b/man2/msync.2 @@ -49,7 +49,7 @@ is updated. The .I flags argument should specify exactly one of -.BR MS_ASYNC +.B MS_ASYNC and .BR MS_SYNC , and may additionally include the @@ -122,9 +122,9 @@ to a value greater than 0. .\" glibc defines them to 1. .SH NOTES According to POSIX, either -.BR MS_SYNC +.B MS_SYNC or -.BR MS_ASYNC +.B MS_ASYNC must be specified in .IR flags , and indeed failure to include one of these flags will cause @@ -137,14 +137,14 @@ with semantics that are (currently) equivalent to specifying .BR MS_ASYNC . (Since Linux 2.6.19, .\" commit 204ec841fbea3e5138168edbc3a76d46747cc987 -.BR MS_ASYNC +.B MS_ASYNC is in fact a no-op, since the kernel properly tracks dirty pages and flushes them to storage as necessary.) Notwithstanding the Linux behavior, portable, future-proof applications should ensure that they specify either -.BR MS_SYNC +.B MS_SYNC or -.BR MS_ASYNC +.B MS_ASYNC in .IR flags . .SH SEE ALSO -- 2.20.1 -- Bjarni I. Gislason
