Hi Aleksa,

On Wed, Aug 06, 2025 at 02:25:47AM +1000, Aleksa Sarai wrote:

As with openat2(2type), it makes sense to move this to a separate man

I guess you meant open_how(2type) instead of openat2(2type).

	$ find man/man2type/
	man/man2type/
	man/man2type/open_how.2type

page. In addition, future man pages added in this patchset will want to

Please use two spaces after period in commit messages.  See:

$ cat CONTRIBUTING.d/patches/description | grep -A5 Style.guide
    Style guide
	URIs should always be enclosed in <>.

	The correct inter-sentence space amount is two.  See some
	history about this:
	<https://web.archive.org/web/20171217060354/http://www.heracliteanriver.com/?p=324>

Please use .member syntax.  This is the convention we're using for new
documentation.  I'll slowly add consistency to the existing docs.  So:

	.I .attr_set

+This field specifies which
+.B MOUNT_ATTR_*

Please use

	.BI MOUNT_ATTR_ *

The variable part should be in italics.

+attribute flags to set.
+.TP
+.I attr_clr
+This fields specifies which
+.B MOUNT_ATTR_*

Same here.

+attribute flags to clear.
+.TP
+.I propagation
+This field specifies what mount propagation will be applied.
+The valid values of this field are the same propagation types described in
+.BR mount_namespaces (7).
+.TP
+.I userns_fd
+This fields specifies a file descriptor that indicates which user namespace to
+use as a reference for ID-mapped mounts with
+.BR MOUNT_ATTR_IDMAP .
+.SH VERSIONS
+Extra fields may be appended to the structure, with a zero value in a new field

Please use semantic newlines.  That is, break after the comma.  See
man-pages(7):

$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
   Use semantic newlines
       In the source of a manual page, new sentences should be  started
       on  new  lines,  long  sentences  should  be split into lines at
       clause breaks (commas, semicolons, colons, and so on), and  long
       clauses  should be split at phrase boundaries.  This convention,
       sometimes known as "semantic newlines", makes it easier  to  see
       the effect of patches, which often operate at the level of indi‐
       vidual sentences, clauses, or phrases.


Have a lovely day!
Alex

+resulting in the kernel behaving as though that extension field was not
+present.
+Therefore, a user
+.I must
+zero-fill this structure on initialization.
+.SH STANDARDS
+Linux.
+.SH SEE ALSO
+.BR mount_setattr (2)

-- 
2.50.1

-- 
<https://www.alejandro-colomar.es/>