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

mount_setattr.2: Minor fixes 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-08-11 00:28:43 +02:00
parent 70a9d0fe1b
commit 5303eb87ee
1 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
man2/mount_setattr.2
View File

@ -97,9 +97,9 @@ argument should usually be specified as
However, if the caller is using a kernel that supports an extended However, if the caller is using a kernel that supports an extended
.IR "struct mount_attr" , .IR "struct mount_attr" ,
but the caller does not intend to make use of these features, but the caller does not intend to make use of these features,
they can pass the size of an earlier it is possible to pass the size of an earlier
version of the structure together with the extended structure. version of the structure together with the extended structure.
This allows the kernel to not copy later parts of the struct This allows the kernel to not copy later parts of the structure
that aren't used anyway. that aren't used anyway.
With each extension that changes the size of With each extension that changes the size of
.IR "struct mount_attr" , .IR "struct mount_attr" ,
@ -431,7 +431,7 @@ isn't a mount point.
.TP .TP
.B EINVAL .B EINVAL
An unsupported value was set in An unsupported value was set in
.I flags. .IR flags .
.TP .TP
.B EINVAL .B EINVAL
An unsupported value was specified in the An unsupported value was specified in the
@ -587,8 +587,8 @@ change ownership in a temporary and localized way.
It is a localized change because the ownership changes are It is a localized change because the ownership changes are
visible only via a specific mount. visible only via a specific mount.
All other users and locations where the filesystem is exposed are unaffected. All other users and locations where the filesystem is exposed are unaffected.
And it is a temporary change because It is a temporary change because
ownership changes are tied to the lifetime of the mount. the ownership changes are tied to the lifetime of the mount.
.PP .PP
Whenever callers interact with the filesystem through an ID-mapped mount, Whenever callers interact with the filesystem through an ID-mapped mount,
the ID mapping of the mount will be applied to the ID mapping of the mount will be applied to
@ -665,16 +665,15 @@ If any user IDs or group IDs are not mapped,
all files owned by that unmapped user or group ID will appear as all files owned by that unmapped user or group ID will appear as
being owned by the overflow user ID or overflow group ID respectively. being owned by the overflow user ID or overflow group ID respectively.
.PP .PP
Further details and instructions for setting up ID mappings can be found in the Further details on setting up ID mappings can be found in
.BR user_namespaces (7) .BR user_namespaces (7).
man page.
.PP .PP
In the common case, the user namespace passed in In the common case, the user namespace passed in
.I userns_fd .I userns_fd
together with (together with
.B MOUNT_ATTR_IDMAP .B MOUNT_ATTR_IDMAP
in in
.I attr_set .IR attr_set )
to create an ID-mapped mount will be the user namespace of a container. to create an ID-mapped mount will be the user namespace of a container.
In other scenarios it will be a dedicated user namespace associated with In other scenarios it will be a dedicated user namespace associated with
a user's login session as is the case for portable home directories in a user's login session as is the case for portable home directories in