From: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Alejandro Colomar <alx@kernel.org>,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH] statx.2: Document STATX_SUBVOL
Date: Mon, 11 Mar 2024 16:31:36 -0400 [thread overview]
Message-ID: <20240311203221.2118219-1-kent.overstreet@linux.dev> (raw)
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)
.TE
.in
.P
@@ -439,6 +442,11 @@ or 0 if direct I/O is not supported on this file.
This will only be nonzero if
.I stx_dio_mem_align
is nonzero, and vice versa.
+.TP
+.I stx_subvolume
+Subvolume number of the current file.
+
+Subvolumes are fancy directories, i.e. they form a tree structure that may be walked recursively.
.P
For further information on the above fields, see
.BR inode (7).
--
2.43.0
next reply other threads:[~2024-03-11 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 20:31 Kent Overstreet [this message]
2024-03-12 2:19 ` [PATCH] statx.2: Document STATX_SUBVOL Eric Biggers
2024-03-15 13:47 ` Alejandro Colomar
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=20240311203221.2118219-1-kent.overstreet@linux.dev \
--to=kent.overstreet@linux.dev \
--cc=alx@kernel.org \
--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