man*/: srcfix

Found with:

$ grep -rn '"""' man* \
| grep -v '"""""""""""' \
| sed 's/:.*//' \
| sort \
| uniq;
man2/add_key.2
man2/getrlimit.2
man2/keyctl.2
man2/pivot_root.2
man2/request_key.2
man3/isalpha.3
man3/setlocale.3
man3/toupper.3
man7/capabilities.7
man7/cgroups.7
man7/keyrings.7
man7/locale.7
man7/user_namespaces.7

Signed-off-by: Alejandro Colomar <alx@kernel.org>

5 files changed, 34 insertions, 34 deletions

diff --git a/man7/capabilities.7 b/man7/capabilities.7
index ab9379978..b86ef7af0 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1683,7 +1683,7 @@ prctl(PR_SET_SECUREBITS,
 .in
 .\"
 .\"
-.SS Per-user-namespace """set-user-ID-root""" programs
+.SS Per-user-namespace \[dq]set-user-ID-root\[dq] programs
 A set-user-ID program whose UID matches the UID that
 created a user namespace will confer capabilities
 in the process's permitted and effective sets
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index d4e559302..ca10cf859 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -805,7 +805,7 @@ then the corresponding controller-interface files (e.g.,
 are automatically created in the children of that cgroup
 and can be used to exert resource control in the child cgroups.
 .\"
-.SS Cgroups v2 """no internal processes""" rule
+.SS Cgroups v2 \[dq]no internal processes\[dq] rule
 Cgroups v2 enforces a so-called "no internal processes" rule.
 Roughly speaking, this rule means that,
 with the exception of the root cgroup, processes may reside
@@ -974,10 +974,10 @@ fails with the error
 .BR EAGAIN ).
 .IP
 Writing the string
-.I """max"""
+.I \[dq]max\[dq]
 to this file means that no limit is imposed.
 The default value in this file is
-.IR """max""" .
+.IR \[dq]max\[dq] .
 .TP
 .IR cgroup.max.descendants " (since Linux 4.14)"
 .\" commit 1a926e0bbab83bae8207d05a533173425e0496d1
@@ -989,10 +989,10 @@ fails with the error
 .BR EAGAIN ).
 .IP
 Writing the string
-.I """max"""
+.I \[dq]max\[dq]
 to this file means that no limit is imposed.
 The default value in this file is
-.IR """max""" .
+.IR \[dq]max\[dq] .
 .\"
 .SH CGROUPS DELEGATION: DELEGATING A HIERARCHY TO A LESS PRIVILEGED USER
 In the context of cgroups,
@@ -1327,7 +1327,7 @@ The only thing that can be done with this cgroup (other than deleting it)
 is to convert it to a
 .I threaded
 cgroup by writing the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to the
 .I cgroup.type
 file.
@@ -1369,7 +1369,7 @@ There are two pathways that lead to the creation of a threaded subtree.
 The first pathway proceeds as follows:
 .IP (1) 5
 We write the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to the
 .I cgroup.type
 file of a cgroup
@@ -1406,7 +1406,7 @@ will also have the type
 .RE
 .IP (2)
 We write the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to each of the
 .I domain invalid
 cgroups under
@@ -1418,7 +1418,7 @@ now have the type
 .I threaded
 and the threaded subtree is now fully usable.
 The requirement to write
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to each of these cgroups is somewhat cumbersome,
 but allows for possible future extensions to the thread-mode model.
 .P
@@ -1449,7 +1449,7 @@ are converted to type
 .RE
 .IP (2)
 As before, we make the threaded subtree usable by writing the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to each of the
 .I domain invalid
 cgroups under
@@ -1553,7 +1553,7 @@ A number of rules apply when writing to the
 file:
 .IP \[bu] 3
 Only the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 may be written.
 In other words, the only explicit transition that is possible is to convert a
 .I domain
@@ -1561,7 +1561,7 @@ cgroup to type
 .IR threaded .
 .IP \[bu]
 The effect of writing
-.I """threaded"""
+.I \[dq]threaded\[dq]
 depends on the current value in
 .IR cgroup.type ,
 as follows:
@@ -1607,20 +1607,20 @@ No domain controllers may be enabled in
 file.
 .P
 If any of the above constraints is violated, then an attempt to write
-.I """threaded"""
+.I \[dq]threaded\[dq]
 to a
 .I cgroup.type
 file fails with the error
 .BR ENOTSUP .
 .\"
-.SS The """domain threaded""" cgroup type
+.SS The \[dq]domain threaded\[dq] cgroup type
 According to the pathways described above,
 the type of a cgroup can change to
 .I domain threaded
 in either of the following cases:
 .IP \[bu] 3
 The string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 is written to a child cgroup.
 .IP \[bu]
 A threaded controller is enabled inside the cgroup and
@@ -1666,7 +1666,7 @@ and
 .I threaded
 cgroups.
 If the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
 is written to the
 .I cgroup.type
 file of one of the children of the root cgroup, then
@@ -1690,7 +1690,7 @@ allow a threaded cgroup that employs the
 controller to be placed as high as possible in the hierarchy,
 so as to minimize the (small) cost of traversing the cgroup hierarchy.
 .\"
-.SS The cgroups v2 """cpu""" controller and realtime threads
+.SS The cgroups v2 \[dq]cpu\[dq] controller and realtime threads
 As at Linux 4.19, the cgroups v2
 .I cpu
 controller does not support control of realtime threads
@@ -1708,7 +1708,7 @@ if all realtime threads are in the root cgroup.
 (If there are realtime threads in nonroot cgroups, then a
 .BR write (2)
 of the string
-.I """+cpu"""
+.I \[dq]+cpu\[dq]
 to the
 .I cgroup.subtree_control
 file fails with the error
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 7d9c4a0cf..96683f545 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -98,7 +98,7 @@ the key is scheduled for garbage collection.
 .SS Key types
 The kernel provides several basic types of key:
 .TP
-.I """keyring"""
+.I \[dq]keyring\[dq]
 .\" Note that keyrings use different fields in struct key in order to store
 .\" their data - index_key instead of type/description and name_link/keys
 .\" instead of payload.
@@ -111,7 +111,7 @@ being garbage collected because nothing refers to them.
 Keyrings with descriptions (names)
 that begin with a period (\[aq].\[aq]) are reserved to the implementation.
 .TP
-.I """user"""
+.I \[dq]user\[dq]
 This is a general-purpose key type.
 The key is kept entirely within kernel memory.
 The payload may be read and updated by user-space applications.
@@ -123,12 +123,12 @@ The description may be any valid string, though it is preferred that it
 start with a colon-delimited prefix representing the service
 to which the key is of interest
 (for instance
-.IR """afs:mykey""" ).
+.IR \[dq]afs:mykey\[dq] ).
 .TP
-.IR """logon""" " (since Linux 3.3)"
+.IR \[dq]logon\[dq] " (since Linux 3.3)"
 .\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
 This key type is essentially the same as
-.IR """user""" ,
+.IR \[dq]user\[dq] ,
 but it does not provide reading (i.e., the
 .BR keyctl (2)
 .B KEYCTL_READ
@@ -138,19 +138,19 @@ This is suitable for storing username-password pairs
 that should not be readable from user space.
 .IP
 The description of a
-.I """logon"""
+.I \[dq]logon\[dq]
 key
 .I must
 start with a non-empty colon-delimited prefix whose purpose
 is to identify the service to which the key belongs.
 (Note that this differs from keys of the
-.I """user"""
+.I \[dq]user\[dq]
 type, where the inclusion of a prefix is recommended but is not enforced.)
 .TP
-.IR """big_key""" " (since Linux 3.13)"
+.IR \[dq]big_key\[dq] " (since Linux 3.13)"
 .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
 This key type is similar to the
-.I """user"""
+.I \[dq]user\[dq]
 key type, but it may hold a payload of up to 1\ MiB in size.
 This key type is useful for purposes such as holding Kerberos ticket caches.
 .IP
@@ -685,16 +685,16 @@ field provides some further information about the key.
 The information that appears here depends on the key type, as follows:
 .RS
 .TP
-.IR """user""" " and " """logon"""
+.IR \[dq]user\[dq] " and " \[dq]logon\[dq]
 The size in bytes of the key payload (expressed in decimal).
 .TP
-.I """keyring"""
+.I \[dq]keyring\[dq]
 The number of keys linked to the keyring,
 or the string
 .I empty
 if there are no keys linked to the keyring.
 .TP
-.I """big_key"""
+.I \[dq]big_key\[dq]
 The payload size in bytes, followed either by the string
 .IR [file] ,
 if the key payload exceeds the threshold that means that the
@@ -707,7 +707,7 @@ indicating that the key is small enough to reside in kernel memory.
 .RE
 .IP
 For the
-.I """.request_key_auth"""
+.I \[dq].request_key_auth\[dq]
 key type
 (authorization key; see
 .BR request_key (2)),
diff --git a/man7/locale.7 b/man7/locale.7
index cfd79b259..5a418ae13 100644
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -131,7 +131,7 @@ functions also obey the environment variable
 .B LANGUAGE
 (containing a colon-separated list of locales)
 if the category is set to a valid locale other than
-.BR """C""" .
+.BR \[dq]C\[dq] .
 This category also affects the behavior of
 .BR catopen (3).
 .TP
diff --git a/man7/user_namespaces.7 b/man7/user_namespaces.7
index 290771af2..ddeb669c3 100644
--- a/man7/user_namespaces.7
+++ b/man7/user_namespaces.7
@@ -289,7 +289,7 @@ allows (since Linux 4.6)
 that process to the mount the cgroup version 2 filesystem and
 cgroup version 1 named hierarchies
 (i.e., cgroup filesystems mounted with the
-.I """none,name="""
+.I \[dq]none,name=\[dq]
 option).
 .P
 Holding