From: Alejandro Colomar <alx@kernel.org>
To: Bhavik Sachdev <b.sachdev1904@gmail.com>
Cc: linux-man@vger.kernel.org, criu@lists.linux.dev,
Andrei Vagin <avagin@gmail.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Jeff Layton <jlayton@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Josef Bacik <josef@toxicpanda.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v1 01/10] man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID
Date: Wed, 11 Feb 2026 14:39:33 +0100 [thread overview]
Message-ID: <aYyF1NWuzxTPr5pE@devuan> (raw)
In-Reply-To: <5cf41ebf2abbcf767807be999790e0e5a6bd5865.1770671863.git.b.sachdev1904@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
Hi Bhavik,
On 2026-02-10T02:47:34+0530, Bhavik Sachdev wrote:
> Document the new mnt_ns_id parameter to struct mnt_id_req and the
> STATMOUNT_MNT_NS_ID flag.
>
> req.mnt_ns_id can be used to query for a mount in a foreign mount
> namespace.
>
> STATMOUNT_MNT_NS_ID can be used to retreive the mnt_ns_id of the mount
> being queried.
>
> The mnt_ns_id parameter description is based on this commit message [1]
> and STATMOUNT_MNT_NS_ID text is based on [2].
>
> Link [1]:
> <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71aacb4c8c3d19da053363a5fe7538a8af082d56>
> Link [2]:
> <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=09b31295f833031c88419550172703d45c5401e3>
>
> Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
> ---
> man/man2/statmount.2 | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/man/man2/statmount.2 b/man/man2/statmount.2
> index cdc96da92..f5c4da122 100644
> --- a/man/man2/statmount.2
> +++ b/man/man2/statmount.2
> @@ -23,9 +23,10 @@ .SH SYNOPSIS
> .P
> .EX
> .B struct mnt_id_req {
> -.BR " __u32 size;" " /* sizeof(struct mnt_id_req) */"
> -.BR " __u64 mnt_id;" " /* The mnt_id being queried */"
> -.BR " __u64 param;" " /* An ORed combination of the STATMOUNT_ constants */"
> +.BR " __u32 size;" " /* sizeof(struct mnt_id_req) */"
> +.BR " __u64 mnt_id;" " /* The mnt_id being queried */"
> +.BR " __u64 param;" " /* An ORed combination of the STATMOUNT_ constants */"
> +.BR " __u32 mnt_ns_id;" " /* The id of mnt_ns to query the mnt_id in */"
> .B };
> .P
> .B struct statmount {
> @@ -47,6 +48,7 @@ .SH SYNOPSIS
> .B " __u64 propagate_from;"
> .B " __u32 mnt_root;"
> .B " __u32 mnt_point;"
> +.B " __u64 mnt_ns_id;"
> .B " char str[];"
> .B };
> .EE
> @@ -59,6 +61,9 @@ .SH SYNOPSIS
> .SH DESCRIPTION
> To access a mount's status,
> the caller must have CAP_SYS_ADMIN in the user namespace.
> +In case of accessing a mount in a foreign mount namespace (specified via
> +.IR req.mnt_ns_id ),
> +the foreign mount namespace should be child of the current namespace.
> .P
> This function returns information about a mount,
> storing it in the buffer pointed to by
> @@ -102,6 +107,7 @@ .SS The mnt_id_req structure
> STATMOUNT_MNT_ROOT /* Want/got mnt_root */
> STATMOUNT_MNT_POINT /* Want/got mnt_point */
> STATMOUNT_FS_TYPE /* Want/got fs_type */
> +STATMOUNT_MNT_NS_ID /* Want/got mnt_ns_id */
> .TE
> .in
> .P
> @@ -130,6 +136,13 @@ .SS The mnt_id_req structure
> as one or more bits may,
> in the future,
> be used to specify an extension to the buffer.
> +.P
> +.I req.mnt_ns_id
> +can be obtained from
> +.B NS_GET_MNTNS_ID
Should this ioctl(2) be documented? I don't find it in any manual page.
You don't need to do it in this patch set, though.
> +.BR ioctl (2)
> +operation and is used to specify a foreign mount namespace in which to query
> +.IR req.mnt_id .
> .SS The returned information
> The status information for the target mount is returned in the
> .I statmount
> @@ -232,6 +245,9 @@ .SS The returned information
> relative to the current root (ie if you are in a
> .BR chroot ).
> It is a null-terminated string.
> +.TP
> +.I smbuf.mnt_ns_id
We should document the Linux version in which this was added. It should
be something like this
.IR smbuf.mnt_ns_id " (since Linux 1.23)"
Have a lovely day!
Alex
> +The unique ID of the mount namespace the mount belongs to.
> .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-11 13:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 21:17 [PATCH v1 00/10] man/man2/statmount.2: Document New Features Bhavik Sachdev
2026-02-09 21:17 ` [PATCH v1 01/10] man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID Bhavik Sachdev
2026-02-11 13:39 ` Alejandro Colomar [this message]
2026-02-09 21:17 ` [PATCH v1 02/10] man/man2/statmount.2: Document STATMOUNT_MNT_OPTS Bhavik Sachdev
2026-02-11 13:43 ` Alejandro Colomar
2026-02-09 21:17 ` [PATCH v1 03/10] man/man2/statmount.2: Document STATMOUNT_FS_SUBTYPE Bhavik Sachdev
2026-02-09 21:17 ` [PATCH v1 04/10] man/man2/statmount.2: Document STATMOUNT_SB_SOURCE Bhavik Sachdev
2026-02-09 21:17 ` [PATCH v1 05/10] man/man2/statmount.2: Document STATMOUNT_OPT_ARRAY Bhavik Sachdev
2026-02-11 13:45 ` Alejandro Colomar
2026-02-09 21:17 ` [PATCH v1 06/10] man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY Bhavik Sachdev
2026-02-11 13:49 ` Alejandro Colomar
2026-02-09 21:17 ` [PATCH v1 07/10] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-11 13:59 ` Alejandro Colomar
2026-02-13 10:05 ` Bhavik Sachdev
2026-02-13 13:31 ` Alejandro Colomar
2026-02-09 21:17 ` [PATCH v1 08/10] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-09 21:17 ` [PATCH v1 09/10] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-11 14:01 ` Alejandro Colomar
2026-02-09 21:17 ` [PATCH v1 10/10] 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=aYyF1NWuzxTPr5pE@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