From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>, Anand Jain <anand.jain@oracle.com>,
Filipe Manana <fdmanana@suse.com>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 09/12] xfs/521: require a real SCRATCH_RTDEV
Date: Wed, 10 Dec 2025 11:54:27 -0800 [thread overview]
Message-ID: <20251210195427.GE94594@frogsfrogsfrogs> (raw)
In-Reply-To: <20251210054831.3469261-10-hch@lst.de>
On Wed, Dec 10, 2025 at 06:46:55AM +0100, Christoph Hellwig wrote:
> Require a real SCRATCH_RTDEV instead of faking one up using a loop
> device, as otherwise the options specified in MKFS_OPTIONS might
> not actually work the configuration.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> tests/xfs/521 | 33 ++++++++-------------------------
> tests/xfs/521.out | 1 -
> 2 files changed, 8 insertions(+), 26 deletions(-)
>
> diff --git a/tests/xfs/521 b/tests/xfs/521
> index 0da05a55a276..5cd6649c50c7 100755
> --- a/tests/xfs/521
> +++ b/tests/xfs/521
> @@ -16,34 +16,16 @@
> . ./common/preamble
> _begin_fstest auto quick realtime growfs
>
> -# Override the default cleanup function.
> -_cleanup()
> -{
> - cd /
> - _scratch_unmount >> $seqres.full 2>&1
> - [ -n "$rt_loop_dev" ] && _destroy_loop_device $rt_loop_dev
> - rm -f $tmp.* $TEST_DIR/$seq.rtvol
> -}
> -
> -# Import common functions.
> . ./common/filter
>
> -# Note that we don't _require_realtime because we synthesize a rt volume
> -# below.
> -_require_scratch_nocheck
> -_require_no_large_scratch_dev
> -
> -echo "Create fake rt volume"
> -truncate -s 400m $TEST_DIR/$seq.rtvol
> -rt_loop_dev=$(_create_loop_device $TEST_DIR/$seq.rtvol)
> +_require_realtime
> +_require_scratch
>
> echo "Format and mount 100m rt volume"
> -export USE_EXTERNAL=yes
> -export SCRATCH_RTDEV=$rtdev
> _scratch_mkfs -r size=100m > $seqres.full
> -_try_scratch_mount || _notrun "Could not mount scratch with synthetic rt volume"
> +_scratch_mount
>
> -# zoned file systems only support zoned size-rounded RT device sizes
> +# zoned file systems only support zone-size aligned RT device sizes
> _require_xfs_scratch_non_zoned
>
> testdir=$SCRATCH_MNT/test-$seq
> @@ -58,7 +40,10 @@ echo "Create some files"
> _pwrite_byte 0x61 0 1m $testdir/original >> $seqres.full
>
> echo "Grow fs"
> -$XFS_GROWFS_PROG $SCRATCH_MNT 2>&1 | _filter_growfs >> $seqres.full
> +# growfs expects sizes in FSB units
> +fsbsize=$(_get_block_size $SCRATCH_MNT)
> +$XFS_GROWFS_PROG -R $((400 * 1024 * 1024 / fsbsize)) $SCRATCH_MNT 2>&1 | \
Hrmm, I wonder if this test should check that SCRATCH_RTDEV is at least
400m? But I guess the old code didn't check that the loop file doesn't
ENOSPC (which is another good reason to get rid of the fakery) so...
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> + _filter_growfs >> $seqres.full
> _scratch_cycle_mount
>
> echo "Recheck 400m rt volume stats"
> @@ -73,8 +58,6 @@ echo "Check filesystem"
> _check_scratch_fs
>
> _scratch_unmount
> -_destroy_loop_device $rt_loop_dev
> -unset rt_loop_dev
>
> # success, all done
> status=0
> diff --git a/tests/xfs/521.out b/tests/xfs/521.out
> index 007ab92c6db2..afd18bb0dc99 100644
> --- a/tests/xfs/521.out
> +++ b/tests/xfs/521.out
> @@ -1,5 +1,4 @@
> QA output created by 521
> -Create fake rt volume
> Format and mount 100m rt volume
> Check rt volume stats
> Create some files
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2025-12-10 19:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 5:46 stop overriding SCRATCH_{,LOG,RT}DEV Christoph Hellwig
2025-12-10 5:46 ` [PATCH 01/12] dmflakey: override SCRATCH_DEV in _init_flakey Christoph Hellwig
2025-12-10 5:46 ` [PATCH 02/12] ext4/006: call e2fsck directly Christoph Hellwig
2025-12-10 19:32 ` Darrick J. Wong
2025-12-11 4:52 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 03/12] common: add a _check_dev_fs helper Christoph Hellwig
2025-12-10 23:24 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 04/12] ext4/032: use _check_dev_fs Christoph Hellwig
2025-12-10 23:24 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 05/12] generic/590: split XFS RT specific bits out Christoph Hellwig
2025-12-10 22:51 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 06/12] xfs/157: don't override SCRATCH_{,LOG,RT}DEV Christoph Hellwig
2025-12-10 20:05 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 07/12] xfs/185: don't use SCRATCH_{,RT}DEV helpers Christoph Hellwig
2025-12-10 20:02 ` Darrick J. Wong
2025-12-11 5:00 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 08/12] xfs/424: don't use SCRATCH_DEV helpers Christoph Hellwig
2025-12-10 19:55 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 09/12] xfs/521: require a real SCRATCH_RTDEV Christoph Hellwig
2025-12-10 19:54 ` Darrick J. Wong [this message]
2025-12-11 4:58 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 10/12] xfs/528: " Christoph Hellwig
2025-12-10 19:52 ` Darrick J. Wong
2025-12-11 4:57 ` Christoph Hellwig
2025-12-10 5:46 ` [PATCH 11/12] xfs/530: " Christoph Hellwig
2025-12-10 19:49 ` Darrick J. Wong
2025-12-11 4:55 ` Christoph Hellwig
2025-12-12 20:00 ` Darrick J. Wong
2025-12-10 5:46 ` [PATCH 12/12] xfs/650: " Christoph Hellwig
2025-12-10 19:45 ` Darrick J. Wong
2025-12-10 22:50 ` Darrick J. Wong
2025-12-11 4:54 ` Christoph Hellwig
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=20251210195427.GE94594@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=anand.jain@oracle.com \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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