Two consecutive IPs without text don't make sense, since they are
paragraph separators. The reason we needed it was that PD 0 was
misplaced.
This extra IP was also causing another problem: we needed to specify
again the indentation of the outer list.
Reported-by: mandoc(1) (make lint-man-mandoc)
Signed-off-by: Alejandro Colomar <alx@kernel.org>
The underlying filesystem must support ID-mapped mounts.
Currently, the following filesystems support ID-mapped mounts:
.\" fs_flags = FS_ALLOW_IDMAP in kernel sources
-.IP
.RS
-.PD 0
.IP \[bu] 3
+.PD 0
.BR xfs (5)
(since Linux 5.12)
.IP \[bu]
(ID-mapped lower and upper layers supported since Linux 5.19)
.PD
.RE
-.IP \[bu] 3
+.IP \[bu]
The mount must not already be ID-mapped.
This also implies that the ID mapping of a mount cannot be altered.
.IP \[bu]
Elements are preceded by a number (index) in square brackets [4], [5].
These represent fields in a set.
The first index will be:
-.IP
.RS
-.PD 0
.TP
.B 0
When it represents fields of a C data structure,
to be consistent with arrays.
+.PD 0
.TP
.B 1
When it represents fields of a file,
an unprivileged user can always decrease a pipe's capacity.
.IP (c)
The accounting and checking against the limits were done as follows:
-.IP
.RS
-.PD 0
.IP (1) 5
+.PD 0
Test whether the user has exceeded the limit.
.IP (2)
Make the new pipe buffer allocation.