From: Anand Jain <asj@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, amir73il@gmail.com, zlang@redhat.com,
hch@infradead.org
Subject: [PATCH v2 3/9] fstests: add _clone_mount_option() helper
Date: Sat, 21 Mar 2026 19:58:24 +0800 [thread overview]
Message-ID: <8121d81f7f91db23a67c3298c274e674352a62f6.1774090817.git.asj@kernel.org> (raw)
In-Reply-To: <cover.1774090817.git.asj@kernel.org>
Adds _clone_mount_option() helper function to handle filesystem-specific
requirements for mounting cloned devices. Abstract the need for -o nouuid
on XFS.
Signed-off-by: Anand Jain <asj@kernel.org>
---
common/rc | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/common/rc b/common/rc
index a8e6af5d1a1b..7ff9815d88e3 100644
--- a/common/rc
+++ b/common/rc
@@ -397,6 +397,20 @@ _scratch_mount_options()
$SCRATCH_DEV $SCRATCH_MNT
}
+_clone_mount_option()
+{
+ local mount_opts=""
+
+ case "$FSTYP" in
+ ext4|xfs|btrfs)
+ mount_opts="-o nouuid"
+ ;;
+ *)
+ esac
+
+ echo $mount_opts
+}
+
_supports_filetype()
{
local dir=$1
--
2.43.0
next prev parent reply other threads:[~2026-03-21 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 11:58 [PATCH v2 0/9] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-03-21 11:58 ` [PATCH v2 1/9] fstests: add _require_nouuid_mountopt() helper Anand Jain
2026-03-21 11:58 ` [PATCH v2 2/9] fstests: add _loop_image_create_clone() helper Anand Jain
2026-03-21 11:58 ` Anand Jain [this message]
2026-03-21 11:58 ` [PATCH v2 4/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-03-21 11:58 ` [PATCH v2 5/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-03-21 11:58 ` [PATCH v2 6/9] fstests: verify f_fsid for " Anand Jain
2026-03-21 11:58 ` [PATCH v2 7/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-03-21 11:58 ` [PATCH v2 8/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-03-21 11:58 ` [PATCH v2 9/9] fstests: verify exportfs file handles " Anand Jain
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=8121d81f7f91db23a67c3298c274e674352a62f6.1774090817.git.asj@kernel.org \
--to=asj@kernel.org \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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