Use a single-font-style macro (".B", ".I") for a single argument.
The output from "nroff" and "groff" is unchanged.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man2/umask.2 | 2 +-
man2/umount.2 | 12 ++++----
man2/unlink.2 | 6 ++--
man2/unshare.2 | 68 +++++++++++++++++++++++-----------------------
man2/userfaultfd.2 | 26 +++++++++---------
man2/utimensat.2 | 12 ++++----
6 files changed, 63 insertions(+), 63 deletions(-)
diff --git a/man2/umask.2 b/man2/umask.2
index e74e8ef06..a421a7ba0 100644
--- a/man2/umask.2
+++ b/man2/umask.2
@@ -135,7 +135,7 @@ Since Linux 4.7, the umask of any process can be viewed via the
field of
.IR /proc/[pid]/status .
Inspecting this field in
-.IR /proc/self/status
+.I /proc/self/status
allows a process to retrieve its umask without at the same time changing it.
.PP
The umask setting also affects the permissions assigned to POSIX IPC objects
diff --git a/man2/umount.2 b/man2/umount.2
index 2db49ed38..daacba9ce 100644
--- a/man2/umount.2
+++ b/man2/umount.2
@@ -69,7 +69,7 @@ If, after aborting requests,
some processes still have active references to the filesystem,
the unmount will still fail.
As at Linux 4.12,
-.BR MNT_FORCE
+.B MNT_FORCE
is supported only on the following filesystems:
9p (since Linux 2.6.16),
ceph (since Linux 2.6.34),
@@ -168,9 +168,9 @@ The kernel could not allocate a free page to copy filenames or data into.
.B EPERM
The caller does not have the required privileges.
.SH VERSIONS
-.BR MNT_DETACH
+.B MNT_DETACH
and
-.BR MNT_EXPIRE
+.B MNT_EXPIRE
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=10092
are available in glibc since version 2.11.
.SH CONFORMING TO
@@ -192,7 +192,7 @@ on systems where every mount point is shared by default.
On such systems,
recursively bind mounting the root directory of the filesystem
onto a subdirectory and then later unmounting that subdirectory with
-.BR MNT_DETACH
+.B MNT_DETACH
will cause every mount in the mount namespace to be lazily unmounted.
.PP
To ensure
@@ -203,9 +203,9 @@ the mount point may be remounted using a
call with a
.I mount_flags
argument that includes both
-.BR MS_REC
+.B MS_REC
and
-.BR MS_PRIVATE
+.B MS_PRIVATE
prior to
.BR umount ()
being called.
diff --git a/man2/unlink.2 b/man2/unlink.2
index 0dd5fec4d..d5ea9a29e 100644
--- a/man2/unlink.2
+++ b/man2/unlink.2
@@ -167,7 +167,7 @@ did not allow search permission.
(See also
.BR path_resolution (7).)
.TP
-.BR EBUSY
+.B EBUSY
The file
.I pathname
cannot be unlinked because it is being used by the system
@@ -295,9 +295,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 BUGS
Infelicities in the protocol underlying NFS can cause the unexpected
diff --git a/man2/unshare.2 b/man2/unshare.2
index bccc964d4..8e4d5328b 100644
--- a/man2/unshare.2
+++ b/man2/unshare.2
@@ -81,9 +81,9 @@ This flag has the same effect as the
flag.
Unshare the cgroup namespace.
Use of
-.BR CLONE_NEWCGROUP
+.B CLONE_NEWCGROUP
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
.TP
.BR CLONE_NEWIPC " (since Linux 2.6.19)"
@@ -95,12 +95,12 @@ Unshare the IPC namespace,
so that the calling process has a private copy of the
IPC namespace which is not shared with any other process.
Specifying this flag automatically implies
-.BR CLONE_SYSVSEM
+.B CLONE_SYSVSEM
as well.
Use of
-.BR CLONE_NEWIPC
+.B CLONE_NEWIPC
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
.TP
.BR CLONE_NEWNET " (since Linux 2.6.24)"
@@ -113,9 +113,9 @@ so that the calling process is moved into a
new network namespace which is not shared
with any previously existing process.
Use of
-.BR CLONE_NEWNET
+.B CLONE_NEWNET
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
.TP
.B CLONE_NEWNS
@@ -134,9 +134,9 @@ Specifying this flag automatically implies
.B CLONE_FS
as well.
Use of
-.BR CLONE_NEWNS
+.B CLONE_NEWNS
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
For further information, see
.BR mount_namespaces (7).
@@ -156,14 +156,14 @@ The first child created by the calling process will have
the process ID 1 and will assume the role of
.BR init (1)
in the new namespace.
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
automatically implies
-.BR CLONE_THREAD
+.B CLONE_THREAD
as well.
Use of
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
For further information, see
.BR pid_namespaces (7).
@@ -182,18 +182,18 @@ with the
.B CLONE_NEWUSER
flag, the caller obtains a full set of capabilities in the new namespace.
.IP
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
requires that the calling process is not threaded; specifying
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
automatically implies
.BR CLONE_THREAD .
Since Linux 3.9,
.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
.\" https://lwn.net/Articles/543273/
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
also automatically implies
.BR CLONE_FS .
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
requires that the user ID and group ID
of the calling process are mapped to user IDs and group IDs in the
user namespace of the calling process at the time of the call.
@@ -210,9 +210,9 @@ Unshare the UTS IPC namespace,
so that the calling process has a private copy of the
UTS namespace which is not shared with any other process.
Use of
-.BR CLONE_NEWUTS
+.B CLONE_NEWUTS
requires the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
capability.
.TP
.BR CLONE_SYSVSEM " (since Linux 2.6.26)
@@ -239,18 +239,18 @@ In addition,
.BR CLONE_THREAD ,
.BR CLONE_SIGHAND ,
and
-.BR CLONE_VM
+.B CLONE_VM
can be specified in
.I flags
if the caller is single threaded (i.e., it is not sharing
its address space with another process or thread).
In this case, these flags have no effect.
(Note also that specifying
-.BR CLONE_THREAD
+.B CLONE_THREAD
automatically implies
.BR CLONE_VM ,
and specifying
-.BR CLONE_VM
+.B CLONE_VM
automatically implies
.BR CLONE_SIGHAND .)
.\" As at 3.9, the following forced implications also apply,
@@ -283,23 +283,23 @@ An invalid bit was specified in
.BR CLONE_THREAD ,
.BR CLONE_SIGHAND ,
or
-.BR CLONE_VM
+.B CLONE_VM
was specified in
.IR flags ,
and the caller is multithreaded.
.TP
.B EINVAL
-.BR CLONE_NEWIPC
+.B CLONE_NEWIPC
was specified in
.IR flags ,
but the kernel was not configured with the
.B CONFIG_SYSVIPC
and
-.BR CONFIG_IPC_NS
+.B CONFIG_IPC_NS
options.
.TP
.B EINVAL
-.BR CLONE_NEWNET
+.B CLONE_NEWNET
was specified in
.IR flags ,
but the kernel was not configured with the
@@ -307,7 +307,7 @@ but the kernel was not configured with the
option.
.TP
.B EINVAL
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
was specified in
.IR flags ,
but the kernel was not configured with the
@@ -315,7 +315,7 @@ but the kernel was not configured with the
option.
.TP
.B EINVAL
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
was specified in
.IR flags ,
but the kernel was not configured with the
@@ -323,7 +323,7 @@ but the kernel was not configured with the
option.
.TP
.B EINVAL
-.BR CLONE_NEWUTS
+.B CLONE_NEWUTS
was specified in
.IR flags ,
but the kernel was not configured with the
@@ -331,13 +331,13 @@ but the kernel was not configured with the
option.
.TP
.B EINVAL
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
was specified in
.IR flags ,
but the process has previously called
.BR unshare ()
with the
-.BR CLONE_NEWPID
+.B CLONE_NEWPID
flag.
.TP
.B ENOMEM
@@ -369,7 +369,7 @@ One of the values in
.I flags
specified the creation of a new user namespace,
but doing so would have caused the limit defined by the corresponding file in
-.IR /proc/sys/user
+.I /proc/sys/user
to be exceeded.
For further details, see
.BR namespaces (7).
@@ -378,7 +378,7 @@ For further details, see
The calling process did not have the required privileges for this operation.
.TP
.B EPERM
-.BR CLONE_NEWUSER
+.B CLONE_NEWUSER
was specified in
.IR flags ,
but either the effective user ID or the effective group ID of the caller
@@ -401,7 +401,7 @@ was specified in
.IR flags ,
and the limit on the number of nested user namespaces would be exceeded.
See the discussion of the
-.BR ENOSPC
+.B ENOSPC
error above.
.SH VERSIONS
The
diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
index e1a8343b3..c5654af16 100644
--- a/man2/userfaultfd.2
+++ b/man2/userfaultfd.2
@@ -55,21 +55,21 @@ used for the creation of the userfaultfd or subsequent calls to
.BR fcntl (2).
.PP
The following values may be bitwise ORed in
-.IR flags
+.I flags
to change the behavior of
.BR userfaultfd ():
.TP
-.BR O_CLOEXEC
+.B O_CLOEXEC
Enable the close-on-exec flag for the new userfaultfd file descriptor.
See the description of the
.B O_CLOEXEC
flag in
.BR open (2).
.TP
-.BR O_NONBLOCK
+.B O_NONBLOCK
Enables non-blocking operation for the userfaultfd object.
See the description of the
-.BR O_NONBLOCK
+.B O_NONBLOCK
flag in
.BR open (2).
.PP
@@ -149,7 +149,7 @@ to determine the API version and supported features.
This operation must be performed before any of the other
.BR ioctl (2)
operations described below (or those operations fail with the
-.BR EINVAL
+.B EINVAL
error).
.PP
After a successful
@@ -299,7 +299,7 @@ Generated when the faulting process invokes
(or
.BR clone (2)
without the
-.BR CLONE_VM
+.B CLONE_VM
flag).
The event details are available in the
.I fork
@@ -317,9 +317,9 @@ field.
Generated when the faulting process invokes
.BR madvise (2)
with
-.BR MADV_DONTNEED
+.B MADV_DONTNEED
or
-.BR MADV_REMOVE
+.B MADV_REMOVE
advice.
The event details are available in the
.I remove
@@ -392,7 +392,7 @@ on a userfaultfd file descriptor can fail with the following errors:
.TP
.B EINVAL
The userfaultfd object has not yet been enabled using the
-.BR UFFDIO_API
+.B UFFDIO_API
.BR ioctl (2)
operation
.PP
@@ -410,7 +410,7 @@ If the
flag is not enabled, then
.BR poll (2)
(always) indicates the file as having a
-.BR POLLERR
+.B POLLERR
condition, and
.BR select (2)
indicates the file descriptor as both readable and writable.
@@ -430,7 +430,7 @@ is set appropriately.
An unsupported value was specified in
.IR flags .
.TP
-.BR EMFILE
+.B EMFILE
The per-process limit on the number of open file descriptors has been
reached
.TP
@@ -457,7 +457,7 @@ Glibc does not provide a wrapper for this system call; call it using
.PP
The userfaultfd mechanism can be used as an alternative to
traditional user-space paging techniques based on the use of the
-.BR SIGSEGV
+.B SIGSEGV
signal and
.BR mmap (2).
It can also be used to implement lazy restore
@@ -756,6 +756,6 @@ main(int argc, char *argv[])
.BR madvise (2),
.BR mmap (2)
.PP
-.IR Documentation/admin-guide/mm/userfaultfd.rst
+.I Documentation/admin-guide/mm/userfaultfd.rst
in the Linux kernel source tree
.PP
diff --git a/man2/utimensat.2 b/man2/utimensat.2
index d61b43e96..c32ce14f3 100644
--- a/man2/utimensat.2
+++ b/man2/utimensat.2
@@ -182,7 +182,7 @@ If
.I pathname
is relative, then by default it is interpreted relative to the
directory referred to by the open file descriptor,
-.IR dirfd
+.I dirfd
(rather than relative to the current working directory of
the calling process, as is done by
.BR utimes (2)
@@ -288,7 +288,7 @@ is not a valid file descriptor.
is a relative pathname, but
.I dirfd
is neither
-.BR AT_FDCWD
+.B AT_FDCWD
nor a valid file descriptor.
.TP
.B EFAULT
@@ -380,7 +380,7 @@ and either:
the caller's effective user ID does not match the owner of file,
and the caller is not privileged
(Linux: does not have the
-.BR CAP_FOWNER
+.B CAP_FOWNER
capability); or,
.IP *
.\" Linux 2.6.22 was broken here:
@@ -452,7 +452,7 @@ fields are specified as
then the Linux implementation of
.BR utimensat ()
succeeds even if the file referred to by
-.IR dirfd
+.I dirfd
and
.I pathname
does not exist.
@@ -485,7 +485,7 @@ Note, however, that the glibc wrapper for
disallows passing NULL as the value for
.IR pathname :
the wrapper function returns the error
-.IR EINVAL
+.I EINVAL
in this case.
.SH BUGS
Several bugs afflict
@@ -515,7 +515,7 @@ Various bugs mean that for the purposes of permission checking,
the case where both
.I tv_nsec
fields are set to
-.BR UTIME_NOW
+.B UTIME_NOW
isn't always treated the same as specifying
.I times
as NULL,
--
2.20.1
