All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 8/8] common: fix _require_xfs_io_command pwrite -A for various blocksizes
Date: Thu, 30 Oct 2025 11:33:33 +0530	[thread overview]
Message-ID: <20ae71dc-c279-42fe-bcce-1b271f487a2e@gmail.com> (raw)
In-Reply-To: <20251024221647.GW6178@frogsfrogsfrogs>


On 10/25/25 03:46, Darrick J. Wong wrote:
> On Fri, Oct 24, 2025 at 02:48:00PM +0530, Nirjhar Roy (IBM) wrote:
>> On Wed, 2025-10-15 at 09:38 -0700, Darrick J. Wong wrote:
>>> From: Darrick J. Wong <djwong@kernel.org>
>>>
>>> In this predicate, we should test an atomic write of the minimum
>>> supported size, not just 4k.  This fixes a problem where none of the
>>> atomic write tests actually run on a 32k-fsblock xfs because you can't
>>> do a sub-fsblock atomic write.
>>>
>>> Cc: <fstests@vger.kernel.org> # v2025.04.13
>>> Fixes: d90ee3b6496346 ("generic: add a test for atomic writes")
>>> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
>>> ---
>>>   common/rc |   14 +++++++++++---
>>>   1 file changed, 11 insertions(+), 3 deletions(-)
>>>
>>>
>>> diff --git a/common/rc b/common/rc
>>> index 1b78cd0c358bb9..dcae5bc33b19ce 100644
>>> --- a/common/rc
>>> +++ b/common/rc
>>> @@ -3030,16 +3030,24 @@ _require_xfs_io_command()
>>>   	"pwrite")
>>>   		# -N (RWF_NOWAIT) only works with direct vectored I/O writes
>>>   		local pwrite_opts=" "
>>> +		local write_size="4k"
>>>   		if [ "$param" == "-N" ]; then
>>>   			opts+=" -d"
>>> -			pwrite_opts+="-V 1 -b 4k"
>>> +			pwrite_opts+="-V 1 -b $write_size"
>> Nit: We can still keep this to 4k (or any random size and not necessarily a size = fsblocksize),
>> right?
> Well, yes, the default will still be 4k on an old kernel that doesn't
> support STATX_WRITE_ATOMIC.  For kernels that do support that flag,
> write_size will now be whatever the filesystem claims is the minimum
> write unit.

Okay.

--NR

>
>>>   		fi
>>>   		if [ "$param" == "-A" ]; then
>>>   			opts+=" -d"
>>> -			pwrite_opts+="-V 1 -b 4k"
>>> +			# try to write the minimum supported atomic write size
>>> +			write_size="$($XFS_IO_PROG -f -c "statx -r -m $STATX_WRITE_ATOMIC" $testfile 2>/dev/null | \
>>> +				grep atomic_write_unit_min | \
>>> +				grep -o '[0-9]\+')"
>>> +			if [ -z "$write_size" ] || [ "$write_size" = "0" ]; then
>>> +				write_size="0 --not-supported"
>>> +			fi
>>> +			pwrite_opts+="-V 1 -b $write_size"
>>>   		fi
>>>   		testio=`$XFS_IO_PROG -f $opts -c \
>>> -		        "pwrite $pwrite_opts $param 0 4k" $testfile 2>&1`
>>> +		        "pwrite $pwrite_opts $param 0 $write_size" $testfile 2>&1`
>> This looks good to me:
>>
>> Reviewed-by: Nirjhar Roy (IBM) <nirjhar.roy.lists@gmail.com>
> Thanks!
>
> --D
>
>>>   		param_checked="$pwrite_opts $param"
>>>   		;;
>>>   	"scrub"|"repair")
>>>
>>
-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


      reply	other threads:[~2025-10-30  6:04 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 16:36 [PATCHSET] fstests: more random fixes for v2025.10.05 Darrick J. Wong
2025-10-15 16:36 ` [PATCH 1/8] generic/427: try to ensure there's some free space before we do the aio test Darrick J. Wong
2025-10-17  4:18   ` Christoph Hellwig
2025-10-20 14:16   ` Zorro Lang
2025-10-20 18:35     ` Darrick J. Wong
2025-10-15 16:37 ` [PATCH 2/8] common/rc: fix _require_xfs_io_shutdown Darrick J. Wong
2025-10-17  4:18   ` Christoph Hellwig
2025-10-24  7:31   ` Nirjhar Roy (IBM)
2025-10-24 22:08     ` Darrick J. Wong
2025-10-30  6:31       ` Nirjhar Roy (IBM)
2025-10-15 16:37 ` [PATCH 3/8] generic/742: avoid infinite loop if no fiemap results Darrick J. Wong
2025-10-17  4:19   ` Christoph Hellwig
2025-10-15 16:37 ` [PATCH 4/8] generic/{482,757}: skip test if there are no FUA writes Darrick J. Wong
2025-10-17  4:22   ` Christoph Hellwig
2025-10-17 16:24     ` Darrick J. Wong
2025-10-20  6:59       ` Christoph Hellwig
2025-10-15 16:38 ` [PATCH 5/8] generic/772: actually check for file_getattr special file support Darrick J. Wong
2025-10-17  4:23   ` Christoph Hellwig
2025-10-17 17:46   ` Zorro Lang
2025-10-17 22:54     ` Darrick J. Wong
2025-10-18  7:57       ` Zorro Lang
2025-10-20 16:26         ` Darrick J. Wong
2025-10-24  7:44   ` Nirjhar Roy (IBM)
2025-10-24 22:10     ` Darrick J. Wong
2025-10-30  6:05       ` Nirjhar Roy (IBM)
2025-10-30 16:33         ` Darrick J. Wong
2025-10-15 16:38 ` [PATCH 6/8] common/filter: fix _filter_file_attributes to handle xfs file flags Darrick J. Wong
2025-10-17  4:23   ` Christoph Hellwig
2025-10-17 16:22     ` Darrick J. Wong
2025-10-20  7:01       ` Christoph Hellwig
2025-10-20 16:37         ` Darrick J. Wong
2025-10-21  5:30           ` Christoph Hellwig
2025-10-21 14:47             ` Darrick J. Wong
2025-10-15 16:38 ` [PATCH 7/8] common/attr: fix _require_noattr2 Darrick J. Wong
2025-10-17  4:24   ` Christoph Hellwig
2025-10-17 17:13   ` Zorro Lang
2025-10-17 22:55     ` Darrick J. Wong
2025-10-18 14:43       ` Zorro Lang
2025-10-20 16:27         ` Darrick J. Wong
2025-10-24  9:01   ` Nirjhar Roy (IBM)
2025-10-24 22:15     ` Darrick J. Wong
2025-10-30  6:02       ` Nirjhar Roy (IBM)
2025-10-15 16:38 ` [PATCH 8/8] common: fix _require_xfs_io_command pwrite -A for various blocksizes Darrick J. Wong
2025-10-17  4:24   ` Christoph Hellwig
2025-10-24  9:18   ` Nirjhar Roy (IBM)
2025-10-24 22:16     ` Darrick J. Wong
2025-10-30  6:03       ` Nirjhar Roy (IBM) [this message]

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=20ae71dc-c279-42fe-bcce-1b271f487a2e@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.