public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 06/10] man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY
Date: Wed, 11 Feb 2026 14:49:39 +0100	[thread overview]
Message-ID: <aYyIAQxaZCHKwSDx@devuan> (raw)
In-Reply-To: <7d13e42ff9e236116366ba98773a9cecf097b211.1770671863.git.b.sachdev1904@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3757 bytes --]

On 2026-02-10T02:47:39+0530, Bhavik Sachdev wrote:
> Document STATMOUNT_OPT_SEC_ARRAY flag and the corresponding fields
> introduced by it. This text is based this commit message [1].
> 
> Retrieves only security options separated by null bytes.
> 
> Link [1]:
> <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aefff51e1c2986e16f2780ca8e4c97b784800ab5>
> 
> Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
> ---
>  man/man2/statmount.2 | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/man/man2/statmount.2 b/man/man2/statmount.2
> index e47af22c3..b7acde8f4 100644
> --- a/man/man2/statmount.2
> +++ b/man/man2/statmount.2
> @@ -54,6 +54,8 @@ .SH SYNOPSIS
>  .B "    __u32  sb_source;"
>  .B "    __u32  opt_num;"
>  .B "    __u32  opt_array;"
> +.B "    __u32  opt_sec_num;"
> +.B "    __u32  opt_sec_array;"
>  .B "    char   str[];"
>  .B };
>  .EE
> @@ -117,6 +119,7 @@ .SS The mnt_id_req structure
>  STATMOUNT_FS_SUBTYPE	/* Want/got fs_subtype */
>  STATMOUNT_SB_SOURCE	/* Want/got sb_source */
>  STATMOUNT_OPT_ARRAY	/* Want/got opt_... */
> +STATMOUNT_OPT_SEC_ARRAY	/* Want/got opt_sec... */
>  .TE
>  .in
>  .P
> @@ -287,6 +290,15 @@ .SS The returned information
>  buffer that contains file system options separated by null bytes.
>  They can be iterated over the help of
>  .IR smbuf.opt_num .
> +.I smbuf.opt_sec_num

Missing .TP above this.  You could check patches with diffman-git(1) to
check that they look good.

See for example how it shows the effects of this patch:

	$ MANWIDTH=64 diffman-git HEAD
	<standard input>:109: warning: table wider than line length minus indentation
	<standard input>:111: warning: table wider than line length minus indentation
	--- HEAD^:man/man2/statmount.2
	+++ HEAD:man/man2/statmount.2
	@@ -48,6 +48,8 @@ SYNOPSIS
		  __u32  sb_source;
		  __u32  opt_num;
		  __u32  opt_array;
	+         __u32  opt_sec_num;
	+         __u32  opt_sec_array;
		  char   str[];
	      };
	 
	@@ -93,6 +95,7 @@ DESCRIPTION
		  STATMOUNT_FS_SUBTYPE       /* Want/got fs_subtype */
		  STATMOUNT_SB_SOURCE        /* Want/got sb_source */
		  STATMOUNT_OPT_ARRAY        /* Want/got opt_... */
	+         STATMOUNT_OPT_SEC_ARRAY    /* Want/got opt_sec... */
	 
	      In general, the kernel does not reject values in req.param
	      other than the above.  (For an exception, see EINVAL in
	@@ -218,7 +221,14 @@ DESCRIPTION
		     The offset to the location in the smbuf.str buffer
		     that contains file system options separated by null
		     bytes.  They can be iterated over the help of sm‐
	-            buf.opt_num.
	+            buf.opt_num.  smbuf.opt_sec_num The number of secu‐
	+            rity options set on the mount.
	+
	+     smbuf.opt_sec_array
	+            The offset to the location in the smbuf.str buffer
	+            that contains security options separated by null
	+            bytes.  They can be iterated over the help of sm‐
	+            buf.opt_sec_num.
	 
	 RETURN VALUE
	      On success, zero is returned.  On error, -1 is returned,

The diffman-git(1) script is part of the repository.  You can install
it with `make -R install`.  Or you can use it directly from src/bin/.


Cheers,
Alex

> +The number of security options set on the mount.
> +.TP
> +.I smbuf.opt_sec_array
> +The offset to the location in the
> +.I smbuf.str
> +buffer that contains security options separated by null bytes.
> +They can be iterated over the help of
> +.IR smbuf.opt_sec_num .
>  .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 --]

  reply	other threads:[~2026-02-11 13:49 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
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 [this message]
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=aYyIAQxaZCHKwSDx@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