From: John Garry <john.g.garry@oracle.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
djwong@kernel.org, ritesh.list@gmail.com
Subject: Re: [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support
Date: Thu, 5 Dec 2024 09:33:18 +0000 [thread overview]
Message-ID: <430694cf-9e34-41d4-9839-9d11db8515fb@oracle.com> (raw)
In-Reply-To: <20241204204553.j7e3nzcbkqzeikou@devuan>
On 04/12/2024 20:45, Alejandro Colomar wrote:
> Hi John,
>
> On Tue, Dec 03, 2024 at 02:53:59PM +0000, John Garry wrote:
>> Linux v6.13 will
>
> Is this already in Linus's tree?
The code to support xfs and ext4 is in Linus' tree from v6.13-rc1, but
v6.13 final is not released yet.
So maybe you want to hold off on this patch until v6.13 final is released.
>
>> 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>
>
> Thanks for the patch! Please see some small comment below.
>
> Have a lovely night!
> Alex
>
>>
>> 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,
>
> There should be a space before the ','.
>
>> +and
>> +.IR stx_atomic_write_segments_max )
How about this:
.B STATX_WRITE_ATOMIC
.RI ( stx_atomic_write_unit_min,
.I stx_atomic_write_unit_max,
and
.IR stx_atomic_write_segments_max )
I think that this looks right.
Thanks,
John
next prev parent reply other threads:[~2024-12-05 9:33 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
2024-12-04 20:45 ` Alejandro Colomar
2024-12-05 9:33 ` John Garry [this message]
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=430694cf-9e34-41d4-9839-9d11db8515fb@oracle.com \
--to=john.g.garry@oracle.com \
--cc=alx@kernel.org \
--cc=djwong@kernel.org \
--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