From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Catherine Hoang <catherine.hoang@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Cc: djwong@kernel.org, john.g.garry@oracle.com
Subject: Re: [PATCH 1/6] generic/765: fix a few issues
Date: Sat, 17 May 2025 08:47:29 +0530 [thread overview]
Message-ID: <87ikm0vsc6.fsf@gmail.com> (raw)
In-Reply-To: <20250514002915.13794-2-catherine.hoang@oracle.com>
Catherine Hoang <catherine.hoang@oracle.com> writes:
> From: "Darrick J. Wong" <djwong@kernel.org>
>
> Fix a few bugs in the single block atomic writes test, such as requiring
> directio, using page size for the ext4 max bsize, and making sure we check
> the max atomic write size.
>
> Cc: ritesh.list@gmail.com
> Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> common/rc | 2 +-
> tests/generic/765 | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index 657772e7..bc8dabc5 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2989,7 +2989,7 @@ _require_xfs_io_command()
> fi
> if [ "$param" == "-A" ]; then
> opts+=" -d"
> - pwrite_opts+="-D -V 1 -b 4k"
> + pwrite_opts+="-d -V 1 -b 4k"
I guess the discussion already happened that this needs fixing.
> fi
> testio=`$XFS_IO_PROG -f $opts -c \
> "pwrite $pwrite_opts $param 0 4k" $testfile 2>&1`
> diff --git a/tests/generic/765 b/tests/generic/765
> index 9bab3b8a..8695a306 100755
> --- a/tests/generic/765
> +++ b/tests/generic/765
> @@ -28,7 +28,7 @@ get_supported_bsize()
> ;;
> "ext4")
> min_bsize=1024
> - max_bsize=4096
> + max_bsize=$(_get_page_size)
> ;;
> *)
> _notrun "$FSTYP does not support atomic writes"
> @@ -73,7 +73,7 @@ test_atomic_writes()
> # Check that atomic min/max = FS block size
> test $file_min_write -eq $bsize || \
> echo "atomic write min $file_min_write, should be fs block size $bsize"
> - test $file_min_write -eq $bsize || \
> + test $file_max_write -eq $bsize || \
> echo "atomic write max $file_max_write, should be fs block size $bsize"
> test $file_max_segments -eq 1 || \
> echo "atomic write max segments $file_max_segments, should be 1"
> --
> 2.34.1
Otherwise the changes looks good. Thanks for fixing this!
-ritesh
next prev parent reply other threads:[~2025-05-17 3:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 0:29 [PATCH 0/6] atomic writes tests Catherine Hoang
2025-05-14 0:29 ` [PATCH 1/6] generic/765: fix a few issues Catherine Hoang
2025-05-14 12:47 ` John Garry
2025-05-14 15:38 ` Darrick J. Wong
2025-05-14 23:42 ` Catherine Hoang
2025-05-15 1:47 ` Darrick J. Wong
2025-05-15 8:16 ` John Garry
2025-05-15 14:54 ` Darrick J. Wong
2025-05-15 17:57 ` John Garry
2025-05-15 21:50 ` Catherine Hoang
2025-05-16 6:59 ` John Garry
2025-05-17 3:17 ` Ritesh Harjani [this message]
2025-05-14 0:29 ` [PATCH 2/6] generic/765: adjust various things Catherine Hoang
2025-05-14 12:59 ` John Garry
2025-05-17 3:36 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 3/6] generic/765: move common atomic write code to a library file Catherine Hoang
2025-05-14 13:00 ` John Garry
2025-05-17 3:49 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 4/6] common/atomicwrites: adjust a few more things Catherine Hoang
2025-05-14 13:11 ` John Garry
2025-05-14 15:40 ` Darrick J. Wong
2025-05-17 3:59 ` Ritesh Harjani
2025-05-14 0:29 ` [PATCH 5/6] common/atomicwrites: fix _require_scratch_write_atomic Catherine Hoang
2025-05-14 13:14 ` John Garry
2025-05-14 0:29 ` [PATCH 6/6] generic: various atomic write tests with scsi_debug Catherine Hoang
2025-05-14 13:41 ` John Garry
2025-05-14 16:01 ` Darrick J. Wong
2025-05-14 16:30 ` John Garry
2025-05-14 23:49 ` Catherine Hoang
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=87ikm0vsc6.fsf@gmail.com \
--to=ritesh.list@gmail.com \
--cc=catherine.hoang@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-xfs@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 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.