From: Alejandro Colomar <alx@kernel.org>
To: Bhavik Sachdev <b.sachdev1904@gmail.com>
Cc: avagin@gmail.com, brauner@kernel.org, criu@lists.linux.dev,
jlayton@kernel.org, josef@toxicpanda.com,
linux-man@vger.kernel.org, miklos@szeredi.hu,
ptikhomirov@virtuozzo.com
Subject: Re: [PATCH v2 1/4] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}
Date: Mon, 23 Feb 2026 16:41:02 +0100 [thread overview]
Message-ID: <aZx02VGlW2GfBdce@devuan> (raw)
In-Reply-To: <2c1e23c24b64c5466075dcf5d4ac1595c04b4139.1771855680.git.b.sachdev1904@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3258 bytes --]
Hi Bhavik,
On 2026-02-23T19:40:23+0530, Bhavik Sachdev wrote:
> Document the STATMOUNT_{UIDMAP,GIDMAP} flags and the corresponding
> fields introduced by them. Most of this is based on the commit message
> provided here [1].
>
> Link [1]:
> <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37c4a9590e1efcae7749682239fc22a330d2d325>
>
> Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
> Message-ID: <6146fa1d59006387ad7996f28f5651787125d956.1771855135.git.b.sachdev1904@gmail.com>
> ---
> Hey Alex!
>
> Hopefully this is what you wanted!
Yup, that was it. :)
I've applied patches v2 1..3. I've done some minor amends, and patch 4
doesn't apply. Would you mind rebasing that one?
Have a lovely day!
Alex
>
> Thanks,
> Bhavik
>
> man/man2/statmount.2 | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/man/man2/statmount.2 b/man/man2/statmount.2
> index f8d2302ef..f5a3721eb 100644
> --- a/man/man2/statmount.2
> +++ b/man/man2/statmount.2
> @@ -56,6 +56,10 @@ .SH SYNOPSIS
> .B " __u32 opt_array;"
> .B " __u32 opt_sec_num;"
> .B " __u32 opt_sec_array;"
> +.B " __u32 mnt_uidmap_num;"
> +.B " __u32 mnt_uidmap;"
> +.B " __u32 mnt_gidmap_num;"
> +.B " __u32 mnt_gidmap;"
> .B " char str[];"
> .B };
> .EE
> @@ -120,6 +124,8 @@ .SS The mnt_id_req structure
> STATMOUNT_SB_SOURCE /* Want/got sb_source */
> STATMOUNT_OPT_ARRAY /* Want/got opt_{num,array} */
> STATMOUNT_OPT_SEC_ARRAY /* Want/got opt_sec_{num,array} */
> +STATMOUNT_MNT_UIDMAP /* Want/got uidmap... */
> +STATMOUNT_MNT_GIDMAP /* Want/got gidmap... */
> .TE
> .in
> .P
> @@ -302,6 +308,38 @@ .SS The returned information
> buffer that contains security options separated by null bytes.
> They can be iterated over with the help of
> .IR smbuf.opt_sec_num .
> +.TP
> +.IR smbuf.mnt_uidmap_num " (since Linux 6.15)"
> +The number of uid mappings applied on the mount.
> +If
> +.I smbuf.mask
> +has STATMOUNT_UIDMAP set and this field is 0,
> +the mount is not an idmapped mount.
> +.TP
> +.IR smbuf.mnt_uidmap " (since Linux 6.15)"
> +The offset to the location in the
> +.I smbuf.str
> +buffer that contains uid mappings as consecutive null-terminated strings.
> +They can be iterated over with the help of
> +.IR smbuf.mnt_uidmap_num .
> +The whole range of uid mappings must be resolvable in the user namespace
> +of the caller.
> +.TP
> +.IR smbuf.mnt_gidmap_num " (since Linux 6.15)"
> +The number of gid mappings applied on the mount.
> +If
> +.I smbuf.mask
> +has STATMOUNT_GIDMAP set and this field is 0,
> +the mount is not an idmapped mount.
> +.TP
> +.IR smbuf.mnt_gidmap " (since Linux 6.15)"
> +The offset to the location in the
> +.I smbuf.str
> +buffer that contains gid mappings as consecutive null-terminated strings.
> +They can be iterated over with the help of
> +.IR smbuf.mnt_gidmap_num .
> +The whole range of gid mappings must be resolvable in the user namespace
> +of the caller.
> .SH RETURN VALUE
> On success, zero is returned.
> On error, \-1 is returned, and
> --
> 2.53.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-23 15:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 14:45 [PATCH v2 00/10] man/man2/statmount.2: Document New Features Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 01/10] man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 02/10] man/man2/statmount.2: Document STATMOUNT_MNT_OPTS Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 03/10] man/man2/statmount.2: Document STATMOUNT_FS_SUBTYPE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 04/10] man/man2/statmount.2: Document STATMOUNT_SB_SOURCE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 05/10] man/man2/statmount.2: Document STATMOUNT_OPT_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 06/10] man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 07/10] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 08/10] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 09/10] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-22 14:46 ` [PATCH v2 10/10] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-22 21:52 ` [PATCH v2 00/10] man/man2/statmount.2: Document New Features Alejandro Colomar
2026-02-23 14:10 ` [PATCH v2 1/4] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-23 15:41 ` Alejandro Colomar [this message]
2026-02-23 18:17 ` [PATCH v2] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-24 0:21 ` Alejandro Colomar
2026-02-26 3:10 ` [PATCH v3] " Bhavik Sachdev
2026-03-04 14:58 ` Alejandro Colomar
2026-03-05 0:13 ` Askar Safin
2026-03-05 0:42 ` Alejandro Colomar
2026-03-05 2:18 ` Aleksa Sarai
2026-03-05 17:19 ` Alejandro Colomar
2026-03-05 22:24 ` G. Branden Robinson
2026-03-05 22:45 ` Alejandro Colomar
2026-03-05 22:55 ` G. Branden Robinson
2026-03-06 7:51 ` Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 2/4] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 3/4] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 4/4] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
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=aZx02VGlW2GfBdce@devuan \
--to=alx@kernel.org \
--cc=avagin@gmail.com \
--cc=b.sachdev1904@gmail.com \
--cc=brauner@kernel.org \
--cc=criu@lists.linux.dev \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-man@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox