user_namespaces.7: Minor wording fix to recently added text

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-07-02 06:20:44 +02:00
parent 43f4bec190
commit 89a0bd8283
1 changed files with 2 additions and 2 deletions

View File

@ -904,12 +904,12 @@ in the user namespace.
The
.BR CAP_FOWNER
capability is treated somewhat exceptionally:
most of the checks that it governs can be bypassed so long as
just the file's user ID has a mapping in the user namespace
.\" These are the checks performed by the kernel function
.\" inode_owner_or_capable(). There is one exception to the exception:
.\" overriding the directory sticky permission bit requires that
.\" the file has a valid mapping for both its UID and GID.
it allows a process to bypass the corresponding rules so long as
at least the file's user ID has a mapping in the user namespace
(i.e., the file's group ID does not need to have a valid mapping).
.\"
.\" ============================================================