From: Alejandro Colomar <alx@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] statx.2: Document STATX_SUBVOL
Date: Fri, 15 Mar 2024 14:47:20 +0100 [thread overview]
Message-ID: <ZfRRaGMO2bngdFOs@debian> (raw)
In-Reply-To: <20240312021908.GC1182@sol.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
Hi!
On Mon, Mar 11, 2024 at 07:19:08PM -0700, Eric Biggers wrote:
> On Mon, Mar 11, 2024 at 04:31:36PM -0400, Kent Overstreet wrote:
> > Document the new statxt.stx_subvol field.
> >
> > This would be clearer if we had a proper API for walking subvolumes that
> > we could refer to, but that's still coming.
> >
> > Link: https://lore.kernel.org/linux-fsdevel/20240308022914.196982-1-kent.overstreet@linux.dev/
> > Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> > Cc: Alejandro Colomar <alx@kernel.org>
> > Cc: linux-man@vger.kernel.org
> > Cc: linux-fsdevel@vger.kernel.org
> > ---
> > man2/statx.2 | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/man2/statx.2 b/man2/statx.2
> > index 0dcf7e20bb1f..480e69b46a89 100644
> > --- a/man2/statx.2
> > +++ b/man2/statx.2
> > @@ -68,6 +68,7 @@ struct statx {
> > /* Direct I/O alignment restrictions */
> > __u32 stx_dio_mem_align;
> > __u32 stx_dio_offset_align;
> > + __u64 stx_subvol; /* Subvolume identifier */
> > };
> > .EE
> > .in
> > @@ -255,6 +256,8 @@ STATX_ALL The same as STATX_BASIC_STATS | STATX_BTIME.
> > STATX_MNT_ID Want stx_mnt_id (since Linux 5.8)
> > STATX_DIOALIGN Want stx_dio_mem_align and stx_dio_offset_align
> > (since Linux 6.1; support varies by filesystem)
> > +STATX_SUBVOL Wants stx_subvol
> > + (since Linux 6.9; support varies by filesystem)
>
> The other ones say "Want", not "Wants".
>
> > +.TP
> > +.I stx_subvolume
>
> It's stx_subvol, not stx_subvolume.
>
> > +Subvolume number of the current file.
> > +
Also, don't use blank lines. We use '.P' for new paragraphs.
> > +Subvolumes are fancy directories, i.e. they form a tree structure that may be walked recursively.
And please use semantic newlines (see man-pages(7)).
Have a lovely day!
Alex
>
> How about documenting which filesystems support it?
>
> - Eric
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-15 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 20:31 [PATCH] statx.2: Document STATX_SUBVOL Kent Overstreet
2024-03-12 2:19 ` Eric Biggers
2024-03-15 13:47 ` Alejandro Colomar [this message]
2024-06-17 7:36 ` John Garry
2024-06-17 8:47 ` Alejandro Colomar
2024-06-18 9:19 ` John Garry
2024-06-18 12:14 ` Alejandro Colomar
2024-11-24 13:35 ` Alejandro Colomar
2024-11-25 9:03 ` John Garry
2024-11-25 10:31 ` Alejandro Colomar
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=ZfRRaGMO2bngdFOs@debian \
--to=alx@kernel.org \
--cc=ebiggers@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).