LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

mount_setattr.2: Minor formatting fixes 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-08-09 06:33:03 +02:00
parent 63097cb7be
commit 03cd41e922
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
man2/mount_setattr.2
View File

@ -379,7 +379,7 @@ and also the following
.BR xattr (7)
keys:
.RS
.IP \(bu
.IP \(bu 3
.IR security.capability ,
whenever filesystem
.BR capabilities (7)
@ -400,7 +400,7 @@ entries.
.IP
The following conditions must be met in order to create an idmapped mount:
.RS
.IP \(bu
.IP \(bu 3
The caller must have
.I CAP_SYS_ADMIN
in the initial user namespace.
@ -465,7 +465,7 @@ for the sake of idmapping a mount.
Idmapped mounts can be useful in the following
and a variety of other scenarios:
.RS
.IP \(bu
.IP \(bu 3
Sharing files between multiple users or multiple machines,
especially in complex scenarios.
For example,
@ -707,7 +707,7 @@ or
set and the flag is locked.
Mount attributes become locked on a mount if:
.RS
.IP \(bu
.IP \(bu 3
A new mount or mount tree is created causing mount propagation across user
namespaces.
The kernel will lock the aforementioned flags to protect these sensitive
@ -778,7 +778,7 @@ and let
.I ksize
be the size of the structure which the kernel supports,
then there are three cases to consider:
.IP \(bu
.IP \(bu 3
If
.I ksize
equals
@ -984,7 +984,7 @@ main(int argc, char *argv[])
ret = move_mount(fd_tree, "", \-EBADF, target,
MOVE_MOUNT_F_EMPTY_PATH);
if (ret == \-1)
exit_log("%m - Failed to attach mount to %s\en", target);
exit_log("%m \- Failed to attach mount to %s\en", target);
close(fd_tree);
exit(EXIT_SUCCESS);