mirror of https://github.com/mkerrisk/man-pages
mount_setattr.2: Minor formatting fixes
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
63097cb7be
commit
03cd41e922
|
@ -379,7 +379,7 @@ and also the following
|
||||||
.BR xattr (7)
|
.BR xattr (7)
|
||||||
keys:
|
keys:
|
||||||
.RS
|
.RS
|
||||||
.IP \(bu
|
.IP \(bu 3
|
||||||
.IR security.capability ,
|
.IR security.capability ,
|
||||||
whenever filesystem
|
whenever filesystem
|
||||||
.BR capabilities (7)
|
.BR capabilities (7)
|
||||||
|
@ -400,7 +400,7 @@ entries.
|
||||||
.IP
|
.IP
|
||||||
The following conditions must be met in order to create an idmapped mount:
|
The following conditions must be met in order to create an idmapped mount:
|
||||||
.RS
|
.RS
|
||||||
.IP \(bu
|
.IP \(bu 3
|
||||||
The caller must have
|
The caller must have
|
||||||
.I CAP_SYS_ADMIN
|
.I CAP_SYS_ADMIN
|
||||||
in the initial user namespace.
|
in the initial user namespace.
|
||||||
|
@ -465,7 +465,7 @@ for the sake of idmapping a mount.
|
||||||
Idmapped mounts can be useful in the following
|
Idmapped mounts can be useful in the following
|
||||||
and a variety of other scenarios:
|
and a variety of other scenarios:
|
||||||
.RS
|
.RS
|
||||||
.IP \(bu
|
.IP \(bu 3
|
||||||
Sharing files between multiple users or multiple machines,
|
Sharing files between multiple users or multiple machines,
|
||||||
especially in complex scenarios.
|
especially in complex scenarios.
|
||||||
For example,
|
For example,
|
||||||
|
@ -707,7 +707,7 @@ or
|
||||||
set and the flag is locked.
|
set and the flag is locked.
|
||||||
Mount attributes become locked on a mount if:
|
Mount attributes become locked on a mount if:
|
||||||
.RS
|
.RS
|
||||||
.IP \(bu
|
.IP \(bu 3
|
||||||
A new mount or mount tree is created causing mount propagation across user
|
A new mount or mount tree is created causing mount propagation across user
|
||||||
namespaces.
|
namespaces.
|
||||||
The kernel will lock the aforementioned flags to protect these sensitive
|
The kernel will lock the aforementioned flags to protect these sensitive
|
||||||
|
@ -778,7 +778,7 @@ and let
|
||||||
.I ksize
|
.I ksize
|
||||||
be the size of the structure which the kernel supports,
|
be the size of the structure which the kernel supports,
|
||||||
then there are three cases to consider:
|
then there are three cases to consider:
|
||||||
.IP \(bu
|
.IP \(bu 3
|
||||||
If
|
If
|
||||||
.I ksize
|
.I ksize
|
||||||
equals
|
equals
|
||||||
|
@ -984,7 +984,7 @@ main(int argc, char *argv[])
|
||||||
ret = move_mount(fd_tree, "", \-EBADF, target,
|
ret = move_mount(fd_tree, "", \-EBADF, target,
|
||||||
MOVE_MOUNT_F_EMPTY_PATH);
|
MOVE_MOUNT_F_EMPTY_PATH);
|
||||||
if (ret == \-1)
|
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);
|
close(fd_tree);
|
||||||
|
|
||||||
exit(EXIT_SUCCESS);
|
exit(EXIT_SUCCESS);
|
||||||
|
|
Loading…
Reference in New Issue