public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@kernel.org>
Cc: Anand Jain <asj@kernel.org>, Filipe Manana <fdmanana@suse.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: [PATCH 03/13] common: add a _check_dev_fs helper
Date: Fri, 12 Dec 2025 09:21:51 +0100	[thread overview]
Message-ID: <20251212082210.23401-4-hch@lst.de> (raw)
In-Reply-To: <20251212082210.23401-1-hch@lst.de>

Add a helper to run the file system checker for a given device, and stop
overloading _check_scratch_fs with the optional device argument that
creates complication around scratch RT and log devices.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
---
 common/dmthin     |  6 +++++-
 common/rc         | 21 +++++++++++++++++----
 tests/btrfs/176   |  4 ++--
 tests/generic/648 |  2 +-
 tests/xfs/601     |  2 +-
 5 files changed, 26 insertions(+), 9 deletions(-)

diff --git a/common/dmthin b/common/dmthin
index a1e1fb8763c0..3bea828d0375 100644
--- a/common/dmthin
+++ b/common/dmthin
@@ -33,7 +33,11 @@ _dmthin_cleanup()
 _dmthin_check_fs()
 {
 	_unmount $SCRATCH_MNT > /dev/null 2>&1
-	_check_scratch_fs $DMTHIN_VOL_DEV
+	OLD_SCRATCH_DEV=$SCRATCH_DEV
+	SCRATCH_DEV=$DMTHIN_VOL_DEV
+	_check_scratch_fs
+	SCRATCH_DEV=$OLD_SCRATCH_DEV
+	unset OLD_SCRATCH_DEV
 }
 
 # Set up a dm-thin device on $SCRATCH_DEV
diff --git a/common/rc b/common/rc
index c3cdc220a29b..8618f77a00b5 100644
--- a/common/rc
+++ b/common/rc
@@ -3692,14 +3692,14 @@ _check_test_fs()
     esac
 }
 
-_check_scratch_fs()
+# check the file system passed in as $1
+_check_dev_fs()
 {
-    local device=$SCRATCH_DEV
-    [ $# -eq 1 ] && device=$1
+    local device=$1
 
     case $FSTYP in
     xfs)
-	_check_xfs_scratch_fs $device
+	_check_xfs_filesystem $device "none" "none"
 	;;
     udf)
 	_check_udf_filesystem $device $udf_fsize
@@ -3751,6 +3751,19 @@ _check_scratch_fs()
     esac
 }
 
+# check the scratch file system
+_check_scratch_fs()
+{
+	case $FSTYP in
+	xfs)
+		_check_xfs_scratch_fs $SCRATCH_DEV
+		;;
+	*)
+		_check_dev_fs $SCRATCH_DEV
+		;;
+	esac
+}
+
 _full_fstyp_details()
 {
      [ -z "$FSTYP" ] && FSTYP=xfs
diff --git a/tests/btrfs/176 b/tests/btrfs/176
index 86796c8814a0..f2619bdd8e44 100755
--- a/tests/btrfs/176
+++ b/tests/btrfs/176
@@ -37,7 +37,7 @@ swapoff "$SCRATCH_MNT/swap" > /dev/null 2>&1
 # Deleting device 1 should work again after swapoff.
 $BTRFS_UTIL_PROG device delete "$scratch_dev1" "$SCRATCH_MNT"
 _scratch_unmount
-_check_scratch_fs "$scratch_dev2"
+_check_dev_fs "$scratch_dev2"
 
 echo "Replace device"
 _scratch_mkfs >> $seqres.full 2>&1
@@ -55,7 +55,7 @@ swapoff "$SCRATCH_MNT/swap" > /dev/null 2>&1
 $BTRFS_UTIL_PROG replace start -fB "$scratch_dev1" "$scratch_dev2" "$SCRATCH_MNT" \
 	>> $seqres.full
 _scratch_unmount
-_check_scratch_fs "$scratch_dev2"
+_check_dev_fs "$scratch_dev2"
 
 # success, all done
 status=0
diff --git a/tests/generic/648 b/tests/generic/648
index 7473c9d33746..1bba78f062cf 100755
--- a/tests/generic/648
+++ b/tests/generic/648
@@ -133,7 +133,7 @@ if [ -f "$loopimg" ]; then
 		_metadump_dev $DMERROR_DEV $seqres.scratch.final.md
 		echo "final scratch mount failed"
 	fi
-	SCRATCH_RTDEV= SCRATCH_LOGDEV= _check_scratch_fs $loopimg
+	_check_dev_fs $loopimg
 fi
 
 # success, all done; let the test harness check the scratch fs
diff --git a/tests/xfs/601 b/tests/xfs/601
index df382402b958..44911ea389a7 100755
--- a/tests/xfs/601
+++ b/tests/xfs/601
@@ -39,7 +39,7 @@ copy_file=$testdir/copy.img
 
 echo copy
 $XFS_COPY_PROG $SCRATCH_DEV $copy_file >> $seqres.full
-_check_scratch_fs $copy_file
+_check_dev_fs $copy_file
 
 echo recopy
 $XFS_COPY_PROG $copy_file $SCRATCH_DEV >> $seqres.full
-- 
2.47.3


  parent reply	other threads:[~2025-12-12  8:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12  8:21 stop overriding SCRATCH_{,LOG,RT}DEV v2 Christoph Hellwig
2025-12-12  8:21 ` [PATCH 01/13] dmflakey: override SCRATCH_DEV in _init_flakey Christoph Hellwig
2025-12-12 20:11   ` Darrick J. Wong
2025-12-15  5:29     ` Christoph Hellwig
2025-12-15 19:41       ` Darrick J. Wong
2025-12-17 16:59   ` Anand Jain
2025-12-12  8:21 ` [PATCH 02/13] ext4/006: call e2fsck directly Christoph Hellwig
2025-12-12 20:02   ` Darrick J. Wong
2025-12-15  5:27     ` Christoph Hellwig
2025-12-15 19:42       ` Darrick J. Wong
2025-12-17 17:01   ` Anand Jain
2025-12-12  8:21 ` Christoph Hellwig [this message]
2025-12-17 17:01   ` [PATCH 03/13] common: add a _check_dev_fs helper Anand Jain
2025-12-12  8:21 ` [PATCH 04/13] ext4/032: use _check_dev_fs Christoph Hellwig
2025-12-17 17:02   ` Anand Jain
2025-12-12  8:21 ` [PATCH 05/13] generic/590: split XFS RT specific bits out Christoph Hellwig
2025-12-17 17:02   ` Anand Jain
2025-12-12  8:21 ` [PATCH 06/13] xfs/157: don't override SCRATCH_{,LOG,RT}DEV Christoph Hellwig
2025-12-12  8:21 ` [PATCH 07/13] xfs/185: don't use SCRATCH_{,RT}DEV helpers Christoph Hellwig
2025-12-12  8:21 ` [PATCH 08/13] xfs/424: don't use SCRATCH_DEV helpers Christoph Hellwig
2025-12-12  8:21 ` [PATCH 09/13] xfs/521: require a real SCRATCH_RTDEV Christoph Hellwig
2025-12-12  8:21 ` [PATCH 10/13] xfs/521: call _require_scratch_size Christoph Hellwig
2025-12-12 20:01   ` Darrick J. Wong
2025-12-12  8:21 ` [PATCH 11/13] xfs/528: require a real SCRATCH_RTDEV Christoph Hellwig
2025-12-12 20:00   ` Darrick J. Wong
2025-12-12  8:22 ` [PATCH 12/13] xfs/530: " Christoph Hellwig
2025-12-12 20:00   ` Darrick J. Wong
2025-12-12  8:22 ` [PATCH 13/13] xfs/650: " Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2025-12-18  7:29 stop overriding SCRATCH_{,LOG,RT}DEV v3 Christoph Hellwig
2025-12-18  7:30 ` [PATCH 03/13] common: add a _check_dev_fs helper 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=20251212082210.23401-4-hch@lst.de \
    --to=hch@lst.de \
    --cc=asj@kernel.org \
    --cc=djwong@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --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