From: "Darrick J. Wong" <djwong@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: alx@kernel.org, linux-man@vger.kernel.org,
linux-fsdevel@vger.kernel.org, ritesh.list@gmail.com
Subject: Re: [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support
Date: Tue, 3 Dec 2024 20:55:25 -0800 [thread overview]
Message-ID: <20241204045525.GB7864@frogsfrogsfrogs> (raw)
In-Reply-To: <20241203145359.2691972-1-john.g.garry@oracle.com>
On Tue, Dec 03, 2024 at 02:53:59PM +0000, John Garry wrote:
> Linux v6.13 will include atomic write support for xfs and ext4, so update
> STATX_WRITE_ATOMIC commentary to mention that.
>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
>
> diff --git a/man/man2/statx.2 b/man/man2/statx.2
> index c5b5a28ec..2d33998c5 100644
> --- a/man/man2/statx.2
> +++ b/man/man2/statx.2
> @@ -482,6 +482,15 @@ The minimum and maximum sizes (in bytes) supported for direct I/O
> .RB ( O_DIRECT )
> on the file to be written with torn-write protection.
> These values are each guaranteed to be a power-of-2.
> +.IP
> +.B STATX_WRITE_ATOMIC
> +.RI ( stx_atomic_write_unit_min,
> +.RI stx_atomic_write_unit_max,
> +and
> +.IR stx_atomic_write_segments_max )
> +is supported on block devices since Linux 6.11.
> +The support on regular files varies by filesystem;
> +it is supported by xfs and ext4 since Linux 6.13.
woot!
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> .TP
> .I stx_atomic_write_segments_max
> The maximum number of elements in an array of vectors
> --
> 2.31.1
>
next prev parent reply other threads:[~2024-12-04 4:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:53 [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support John Garry
2024-12-04 4:55 ` Darrick J. Wong [this message]
2024-12-04 20:45 ` Alejandro Colomar
2024-12-05 9:33 ` John Garry
2024-12-05 10:02 ` Alejandro Colomar
2024-12-05 10:34 ` G. Branden Robinson
2024-12-05 12:02 ` Alejandro Colomar
2024-12-16 10:35 ` John Garry
2024-12-16 12:38 ` G. Branden Robinson
2024-12-16 12:47 ` Alejandro Colomar
2025-01-04 20:23 ` 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=20241204045525.GB7864@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=alx@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=ritesh.list@gmail.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