All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, patches@lists.linux.dev,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH] fstests: add helper to canonicalize devices used to enable persistent disks
Date: Wed, 19 Jul 2023 23:17:27 -0700	[thread overview]
Message-ID: <20230720061727.2363548-1-mcgrof@kernel.org> (raw)

The filesystem configuration file does not allow you to use symlinks to
devices given the existing sanity checks verify that the target end
device matches the source.

Using a symlink is desirable if you want to enable persistent tests
across reboots. For example you may want to use /dev/disk/by-id/nvme-eui.*
so to ensure that the same drives are used even after reboot. This
is very useful if you are testing for example with a virtualized
environment and are using PCIe passthrough with other qemu NVMe drives
with one or many NVMe drives.

To enable support just add a helper to canonicalize devices prior to
running the tests.

This allows one test runner, kdevops, which I just extended with
support to use real NVMe drives. The drives it uses for the filesystem
configuration optionally is with NVMe eui symlinks so to allow
the same drives to be used over reboots.

Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 check         |  1 +
 common/config | 44 +++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/check b/check
index 89e7e7bf20df..d063d3f498fd 100755
--- a/check
+++ b/check
@@ -734,6 +734,7 @@ function run_section()
 	fi
 
 	get_next_config $section
+	_canonicalize_devices
 
 	mkdir -p $RESULT_BASE
 	if [ ! -d $RESULT_BASE ]; then
diff --git a/common/config b/common/config
index 936ac225f4b1..f5a3815a0435 100644
--- a/common/config
+++ b/common/config
@@ -655,6 +655,47 @@ _canonicalize_mountpoint()
 	echo "$parent/$base"
 }
 
+# Enables usage of /dev/disk/by-id/ symlinks to persist target devices
+# over reboots
+_canonicalize_devices()
+{
+	if [ ! -z "$TEST_DEV" ] && [ -L $TEST_DEV ]; then
+		TEST_DEV=$(realpath -e $TEST_DEV)
+	fi
+
+	if [ ! -z "$SCRATCH_DEV" ] && [ -L $SCRATCH_DEV ]; then
+		SCRATCH_DEV=$(realpath -e $SCRATCH_DEV)
+	fi
+
+	if [ ! -z "$TEST_LOGDEV" ] && [ -L $TEST_LOGDEV ]; then
+		TEST_LOGDEV=$(realpath -e $TEST_LOGDEV)
+	fi
+
+	if [ ! -z "$TEST_RTDEV" ] && [ -L $TEST_RTDEV ]; then
+		TEST_RTDEV=$(realpath -e $TEST_RTDEV)
+	fi
+
+	if [ ! -z "$SCRATCH_RTDEV" ] && [ -L $SCRATCH_RTDEV ]; then
+		SCRATCH_RTDEV=$(realpath -e $SCRATCH_RTDEV)
+	fi
+
+	if [ ! -z "$LOGWRITES_DEV" ] && [ -L $LOGWRITES_DEV ]; then
+		LOGWRITES_DEV=$(realpath -e $LOGWRITES_DEV)
+	fi
+
+	if [ ! -z "$SCRATCH_DEV_POOL" ]; then
+		NEW_SCRATCH_POOL=""
+		for i in $SCRATCH_DEV_POOL; do
+			if [ -L $i ]; then
+				NEW_SCRATCH_POOL="$NEW_SCRATCH_POOL $(realpath -e $i)"
+			else
+				NEW_SCRATCH_POOL="$NEW_SCRATCH_POOL $i)"
+			fi
+		done
+		SCRATCH_DEV_POOL="$NEW_SCRATCH_POOL"
+	fi
+}
+
 # On check -overlay, for the non multi section config case, this
 # function is called on every test, before init_rc().
 # When SCRATCH/TEST_* vars are defined in config file, config file
@@ -785,7 +826,6 @@ get_next_config() {
 	fi
 
 	parse_config_section $1
-
 	if [ ! -z "$OLD_FSTYP" ] && [ $OLD_FSTYP != $FSTYP ]; then
 		[ -z "$MOUNT_OPTIONS" ] && _mount_opts
 		[ -z "$TEST_FS_MOUNT_OPTS" ] && _test_mount_opts
@@ -901,5 +941,7 @@ else
 	fi
 fi
 
+_canonicalize_devices
+
 # make sure this script returns success
 /bin/true
-- 
2.39.2


             reply	other threads:[~2023-07-20  6:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  6:17 Luis Chamberlain [this message]
2023-07-24 10:58 ` [PATCH] fstests: add helper to canonicalize devices used to enable persistent disks Andrey Albershteyn
2023-07-25  8:13 ` Zorro Lang
2023-07-25 15:54   ` Darrick J. Wong
2023-07-25 17:50     ` Zorro Lang
2023-07-26 17:34       ` Luis Chamberlain
2023-07-26  4:41     ` Theodore Ts'o
2023-07-26 16:28       ` Luis Chamberlain
2023-07-27  1:13         ` Theodore Ts'o
2023-07-27  1:26           ` Darrick J. Wong

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=20230720061727.2363548-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    /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.