From: Alejandro Colomar <alx@kernel.org>
To: Bhavik Sachdev <b.sachdev1904@gmail.com>
Cc: avagin@gmail.com, brauner@kernel.org, criu@lists.linux.dev,
linux-man@vger.kernel.org, ptikhomirov@virtuozzo.com
Subject: Re: [PATCH v2 2/2] man/man2/statmount.2: Fix incorrect naming of STATMOUNT_MNT_{UID,GID}MAP flags
Date: Thu, 19 Mar 2026 17:44:58 +0100 [thread overview]
Message-ID: <abwn8ux0V534QVdx@devuan> (raw)
In-Reply-To: <4f6135c8b84b8b291a7145a72f216e77f8cf0103.1773904035.git.b.sachdev1904@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
On 2026-03-19T12:39:12+0530, Bhavik Sachdev wrote:
> STATMOUNT_UIDMAP is actually STATMOUNT_MNT_UIDMAP and STATMOUNT_GIDMAP
> is STATMOUNT_MNT_GIDMAP.
>
> Fixes: 9968ead5 (2026-03-05; "man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}")
> Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
> ---
> Hey Alex!
Hi Bhavik,
> Found another mistake while replying to your comments!
Thanks! I've applied both patches.
Have a lovely day!
Alex
>
> Thanks,
> Bhavik
>
> man/man2/statmount.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man/man2/statmount.2 b/man/man2/statmount.2
> index 78b6e9be..b6d9dc2a 100644
> --- a/man/man2/statmount.2
> +++ b/man/man2/statmount.2
> @@ -355,7 +355,7 @@ .SS The returned information
> The number of uid mappings applied on the mount.
> If
> .I smbuf.mask
> -has STATMOUNT_UIDMAP set and this field is 0,
> +has STATMOUNT_MNT_UIDMAP set and this field is 0,
> then uid mappings applied on the mount
> cannot be resolved in the user namespace of the caller.
> .TP
> @@ -372,7 +372,7 @@ .SS The returned information
> The number of gid mappings applied on the mount.
> If
> .I smbuf.mask
> -has STATMOUNT_GIDMAP set and this field is 0,
> +has STATMOUNT_MNT_GIDMAP set and this field is 0,
> then gid mappings applied on the mount
> cannot be resolved in the user namespace of the caller.
> .TP
> --
> 2.53.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-03-19 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 12:18 [PATCH] man/man2/statmount.2: Fix STATMOUNT_MNT_{UID,GID}MAP documentation Bhavik Sachdev
2026-03-18 0:48 ` Alejandro Colomar
2026-03-19 7:09 ` [PATCH v2 1/2] " Bhavik Sachdev
2026-03-19 7:09 ` [PATCH v2 2/2] man/man2/statmount.2: Fix incorrect naming of STATMOUNT_MNT_{UID,GID}MAP flags Bhavik Sachdev
2026-03-19 16:44 ` Alejandro Colomar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abwn8ux0V534QVdx@devuan \
--to=alx@kernel.org \
--cc=avagin@gmail.com \
--cc=b.sachdev1904@gmail.com \
--cc=brauner@kernel.org \
--cc=criu@lists.linux.dev \
--cc=linux-man@vger.kernel.org \
--cc=ptikhomirov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.