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 08/12] xfs/424: don't use SCRATCH_DEV helpers
Date: Wed, 10 Dec 2025 11:55:55 -0800 [thread overview]
Message-ID: <20251210195555.GF94594@frogsfrogsfrogs> (raw)
In-Reply-To: <20251210054831.3469261-9-hch@lst.de>
On Wed, Dec 10, 2025 at 06:46:54AM +0100, Christoph Hellwig wrote:
> This tests forces external devices to be disabled by calling mkfs.xfs
> directly and overriding SCRATCH_{LOG,RT}DEV, but the options specified in
> MKFS_OPTIONS might not work for this configuration. Instead hard code
> the calls to xfs_db and don't modify the scratch device configuration.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Oh yikes. Yeah, this is more straightforward...
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> tests/xfs/424 | 41 ++++++++++++++++++-----------------------
> 1 file changed, 18 insertions(+), 23 deletions(-)
>
> diff --git a/tests/xfs/424 b/tests/xfs/424
> index 6078d34897e7..61e9de375383 100755
> --- a/tests/xfs/424
> +++ b/tests/xfs/424
> @@ -25,17 +25,11 @@ filter_dbval()
> awk '{ print $4 }'
> }
>
> -# Import common functions.
> . ./common/filter
>
> -# Modify as appropriate
> -
> -# Since we have an open-coded mkfs call, disable the external devices and
> -# don't let the post-check fsck actually run since it'll trip over us not
> -# using the external devices.
> +# Since we have an open-coded mkfs call, don't let the post-check fsck run since
> +# it would trip over us not using the external devices.
> _require_scratch_nocheck
> -export SCRATCH_LOGDEV=
> -export SCRATCH_RTDEV=
>
> echo "Silence is golden."
>
> @@ -62,30 +56,31 @@ for SECTOR_SIZE in $sector_sizes; do
> grep -q 'finobt=1' && finobt_enabled=1
>
> for TYPE in agf agi agfl sb; do
> - DADDR=`_scratch_xfs_db -c "$TYPE" -c "daddr" | filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type $TYPE"
> + DADDR=`$XFS_DB_PROG -c "$TYPE" -c "daddr" $SCRATCH_DEV |
> + filter_dbval`
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type $TYPE" $SCRATCH_DEV
> done
>
> - DADDR=`_scratch_xfs_db -c "sb" -c "addr rootino" -c "daddr" |
> + DADDR=`$XFS_DB_PROG -c "sb" -c "addr rootino" -c "daddr" $SCRATCH_DEV |
> filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type inode"
> - DADDR=`_scratch_xfs_db -c "agf" -c "addr bnoroot" -c "daddr" |
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type inode" $SCRATCH_DEV
> + DADDR=`$XFS_DB_PROG -c "agf" -c "addr bnoroot" -c "daddr" $SCRATCH_DEV |
> filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type bnobt"
> - DADDR=`_scratch_xfs_db -c "agf" -c "addr cntroot" -c "daddr" |
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type bnobt" $SCRATCH_DEV
> + DADDR=`$XFS_DB_PROG -c "agf" -c "addr cntroot" -c "daddr" $SCRATCH_DEV |
> filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type cntbt"
> - DADDR=`_scratch_xfs_db -c "agi" -c "addr root" -c "daddr" |
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type cntbt" $SCRATCH_DEV
> + DADDR=`$XFS_DB_PROG -c "agi" -c "addr root" -c "daddr" $SCRATCH_DEV |
> filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type inobt"
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type inobt" $SCRATCH_DEV
> if [ $finobt_enabled -eq 1 ]; then
> - DADDR=`_scratch_xfs_db -c "agi" -c "addr free_root" -c "daddr" |
> - filter_dbval`
> - _scratch_xfs_db -c "daddr $DADDR" -c "type finobt"
> + DADDR=`$XFS_DB_PROG -c "agi" -c "addr free_root" -c "daddr" $SCRATCH_DEV |
> + filter_dbval`
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type finobt" $SCRATCH_DEV
> fi
>
> - _scratch_xfs_db -c "daddr $DADDR" -c "type text"
> - _scratch_xfs_db -c "daddr $DADDR" -c "type data"
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type text" $SCRATCH_DEV
> + $XFS_DB_PROG -c "daddr $DADDR" -c "type data" $SCRATCH_DEV
> done
>
> # success, all done
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2025-12-10 19:55 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 [this message]
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
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=20251210195555.GF94594@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