Use a single-font-change macro for a single argument. The output from "nroff" and "groff" is unchanged. Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/read.2 | 2 +- man2/readlink.2 | 8 ++++---- man2/readv.2 | 4 ++-- man2/reboot.2 | 4 ++-- man2/recvmmsg.2 | 4 ++-- man2/request_key.2 | 40 ++++++++++++++++++++-------------------- man2/restart_syscall.2 | 8 ++++---- man2/rt_sigqueueinfo.2 | 4 ++-- 8 files changed, 37 insertions(+), 37 deletions(-) diff --git a/man2/read.2 b/man2/read.2 index 6e5123fa4..a42dc8309 100644 --- a/man2/read.2 +++ b/man2/read.2 @@ -106,7 +106,7 @@ and the read would block. See .BR open (2) for further details on the -.BR O_NONBLOCK +.B O_NONBLOCK flag. .TP .BR EAGAIN " or " EWOULDBLOCK diff --git a/man2/readlink.2 b/man2/readlink.2 index e5a934ced..8b0efe0f8 100644 --- a/man2/readlink.2 +++ b/man2/readlink.2 @@ -138,7 +138,7 @@ Since Linux 2.6.39, .I pathname can be an empty string, in which case the call operates on the symbolic link referred to by -.IR dirfd +.I dirfd (which should have been obtained using .BR open (2) with the @@ -268,9 +268,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 EXAMPLE The following program allocates the buffer needed by @@ -278,7 +278,7 @@ The following program allocates the buffer needed by dynamically from the information provided by .BR lstat (2), falling back to a buffer of size -.BR PATH_MAX +.B PATH_MAX in cases where .BR lstat (2) reports a size of zero. diff --git a/man2/readv.2 b/man2/readv.2 index 2d7300750..f51505fb5 100644 --- a/man2/readv.2 +++ b/man2/readv.2 @@ -220,7 +220,7 @@ High priority read/write. Allows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the -.BR O_DIRECT +.B O_DIRECT flag.) .TP .BR RWF_SYNC " (since Linux 4.7)" @@ -243,7 +243,7 @@ system call will return instantly if it would have to read data from the backing storage or wait for a lock. If some data was successfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set -.IR errno +.I errno to .BR EAGAIN . Currently, this flag is meaningful only for diff --git a/man2/reboot.2 b/man2/reboot.2 index 20a7ca44f..7cbaa35d2 100644 --- a/man2/reboot.2 +++ b/man2/reboot.2 @@ -111,7 +111,7 @@ If not preceded by a .BR sync (2), data will be lost. .TP -.BR LINUX_REBOOT_CMD_KEXEC +.B LINUX_REBOOT_CMD_KEXEC .RB ( RB_KEXEC , 0x45584543, since Linux 2.6.13). Execute a kernel that has been loaded earlier with @@ -147,7 +147,7 @@ If not preceded by a .BR sync (2), data will be lost. .TP -.BR LINUX_REBOOT_CMD_SW_SUSPEND +.B LINUX_REBOOT_CMD_SW_SUSPEND .RB ( RB_SW_SUSPEND , 0xd000fce1; since Linux 2.5.18). The system is suspended (hibernated) to disk. diff --git a/man2/recvmmsg.2 b/man2/recvmmsg.2 index 4aee1dc11..0f5e5531d 100644 --- a/man2/recvmmsg.2 +++ b/man2/recvmmsg.2 @@ -34,7 +34,7 @@ recvmmsg \- receive multiple messages on a socket .SH SYNOPSIS .nf .BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */" -.BI "#include <sys/socket.h>" +.B #include <sys/socket.h> .PP .BI "int recvmmsg(int " sockfd ", struct mmsghdr *" msgvec \ ", unsigned int " vlen "," @@ -133,7 +133,7 @@ and returns immediately. On return from .BR recvmmsg (), successive elements of -.IR msgvec +.I msgvec are updated to contain information about each received message: .I msg_len contains the size of the received message; diff --git a/man2/request_key.2 b/man2/request_key.2 index 2487ba648..c24a92e5a 100644 --- a/man2/request_key.2 +++ b/man2/request_key.2 @@ -115,7 +115,7 @@ newly constructed key should be linked, it tries the following keyrings, beginning with the keyring set via the .BR keyctl (2) -.BR KEYCTL_SET_REQKEY_KEYRING +.B KEYCTL_SET_REQKEY_KEYRING operation and continuing in the order shown below until it finds the first keyring that exists: .IP \(bu 3 @@ -188,25 +188,25 @@ This keyring is also expected to always exist. .PP If the .BR keyctl (2) -.BR KEYCTL_SET_REQKEY_KEYRING +.B KEYCTL_SET_REQKEY_KEYRING operation specifies -.BR KEY_REQKEY_DEFL_DEFAULT +.B KEY_REQKEY_DEFL_DEFAULT (or no -.BR KEYCTL_SET_REQKEY_KEYRING +.B KEYCTL_SET_REQKEY_KEYRING operation is performed), then the kernel looks for a keyring starting from the beginning of the list. .\" .SS Requesting user-space instantiation of a key If the kernel cannot find a key matching -.IR type +.I type and .IR description , and .I callout is not NULL, then the kernel attempts to invoke a user-space program to instantiate a key with the given -.IR type +.I type and .IR description . In this case, the following steps are performed: @@ -241,9 +241,9 @@ The key grants .IR view , .IR read , and -.IR search +.I search permissions to the key possessor as well as -.IR view +.I view permission for the key user. .IP * The description (name) of the key is the hexadecimal @@ -296,7 +296,7 @@ The ID of the session keyring of the caller of .IP .IR Note : each of the command-line arguments that is a key ID is encoded in -.IR decimal +.I decimal (unlike the key IDs shown in .IR /proc/keys , which are shown as hexadecimal values). @@ -306,7 +306,7 @@ The program spawned in the previous step: .IP * 3 Assumes the authority to instantiate the key U using the .BR keyctl (2) -.BR KEYCTL_ASSUME_AUTHORITY +.B KEYCTL_ASSUME_AUTHORITY operation (typically via the .BR keyctl_assume_authority (3) function). @@ -314,7 +314,7 @@ function). Obtains the callout data from the payload of the authorization key V (using the .BR keyctl (2) -.BR KEYCTL_READ +.B KEYCTL_READ operation (or, more commonly, the .BR keyctl_read (3) function) with a key ID value of @@ -334,7 +334,7 @@ can be accessed using the special key ID .\" * A key added to that ring is then owned by the requester Instantiation is performed using the .BR keyctl (2) -.BR KEYCTL_INSTANTIATE +.B KEYCTL_INSTANTIATE operation (or, more commonly, the .BR keyctl_instantiate (3) function). @@ -344,7 +344,7 @@ call completes, and the requesting program can continue execution. .RE .PP If these steps are unsuccessful, then an -.BR ENOKEY +.B ENOKEY error will be returned to the caller of .BR request_key () and a temporary, negatively instantiated key will be installed @@ -392,7 +392,7 @@ One of .IR type , .IR description , or -.IR callout_info +.I callout_info points outside the process's accessible address space. .TP .B EINTR @@ -440,7 +440,7 @@ This system call is a nonstandard Linux extension. .SH NOTES No wrapper for this system call is provided in glibc. A wrapper is provided in the -.IR libkeyutils +.I libkeyutils package. When employing the wrapper in that library, link with .IR \-lkeyutils . @@ -451,7 +451,7 @@ The .IR type , .IR description , and -.IR callout_info +.I callout_info arguments for the system call are taken from the values supplied in the command-line arguments. The call specifies the session keyring as the target keyring. @@ -495,7 +495,7 @@ for details of these specifiers. .PP Then we run the program and check the contents of -.IR /proc/keys +.I /proc/keys to verify that the requested key has been instantiated: .PP .in +4n @@ -561,12 +561,12 @@ main(int argc, char *argv[]) .BR request\-key (8) .PP The kernel source files -.IR Documentation/security/keys/core.rst +.I Documentation/security/keys/core.rst and -.IR Documentation/keys/request\-key.rst +.I Documentation/keys/request\-key.rst (or, before Linux 4.13, in the files .\" commit b68101a1e8f0263dbc7b8375d2a7c57c6216fb76 -.IR Documentation/security/keys.txt +.I Documentation/security/keys.txt and .\" commit 3db38ed76890565772fcca3279cc8d454ea6176b .IR Documentation/security/keys\-request\-key.txt ). diff --git a/man2/restart_syscall.2 b/man2/restart_syscall.2 index e7d96bd4d..77943effb 100644 --- a/man2/restart_syscall.2 +++ b/man2/restart_syscall.2 @@ -43,11 +43,11 @@ The .BR restart_syscall () system call is used to restart certain system calls after a process that was stopped by a signal (e.g., -.BR SIGSTOP +.B SIGSTOP or .BR SIGTSTP ) is later resumed after receiving a -.BR SIGCONT +.B SIGCONT signal. This system call is designed only for internal use by the kernel. .PP @@ -63,10 +63,10 @@ when restarted, should adjust their time-related parameters\(emnamely and .BR futex (2), when employed with the -.BR FUTEX_WAIT +.B FUTEX_WAIT (since Linux 2.6.22) and -.BR FUTEX_WAIT_BITSET +.B FUTEX_WAIT_BITSET (since Linux 2.6.31) operations. .\" These system calls correspond to the special internal errno value diff --git a/man2/rt_sigqueueinfo.2 b/man2/rt_sigqueueinfo.2 index c2990b621..6d4d2a2e0 100644 --- a/man2/rt_sigqueueinfo.2 +++ b/man2/rt_sigqueueinfo.2 @@ -88,7 +88,7 @@ with the restriction that the code must be negative which is used by the kernel to indicate a signal sent by .BR kill (2)) and cannot (since Linux 2.6.39) be -.BR SI_TKILL +.B SI_TKILL (which is used by the kernel to indicate a signal sent using .\" tkill(2) or .BR tgkill (2)). @@ -143,7 +143,7 @@ for further information.) .IR sig , .IR tgid , or -.IR tid +.I tid was invalid. .TP .B EPERM -- 2.20.1
