From: Anand Jain <asj@kernel.org>
To: fstests@vger.kernel.org
Cc: zlang@kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 01/21] fstests: introduce _require_clone_mount() helper
Date: Tue, 6 Oct 2026 16:55:27 +0800 [thread overview]
Message-ID: <245314b2efd616b7ecf09f74e2a775e44e10ab43.1791272793.git.asj@kernel.org> (raw)
In-Reply-To: <cover.1791272793.git.asj@kernel.org>
Add _require_clone_mount() to common/rc to check whether the filesystem
supports mounting cloned block devices simultaneously. For Btrfs, it
verifies kernel support for the temp_fsid feature, while skipping
unsupported filesystem types with _notrun.
Signed-off-by: Anand Jain <asj@kernel.org>
---
common/rc | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/common/rc b/common/rc
index 3958ac934980..7868e6d311a2 100644
--- a/common/rc
+++ b/common/rc
@@ -6124,6 +6124,21 @@ _force_inplace_writes()
esac
}
+_require_clone_mount()
+{
+ case "$FSTYP" in
+ xfs|ext4|f2fs)
+ # No kernel-side restriction; always supported
+ ;;
+ btrfs)
+ _require_btrfs_fs_feature "temp_fsid"
+ ;;
+ *)
+ _notrun "$FSTYP does not support mounting cloned devices simultaneously"
+ ;;
+ esac
+}
+
# Test that a filesystem can do writes to a file in place (without allocating
# new extents, without Copy-On-Write semantics).
_require_inplace_writes()
--
2.43.0
next prev parent reply other threads:[~2026-10-06 8:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:55 [PATCH 0/21] fstests: tests for cloned filesystem validation and f_fsid Anand Jain
2026-10-06 8:55 ` Anand Jain [this message]
2026-10-06 8:55 ` [PATCH 02/21] fstests: introduce _create_cloned_loop_devs() helper Anand Jain
2026-10-06 8:55 ` [PATCH 03/21] fstests: add _clone_mount_options() helper Anand Jain
2026-10-06 8:55 ` [PATCH 04/21] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-10-06 8:55 ` [PATCH 05/21] fstests: add _require_fanotify_function Anand Jain
2026-10-06 8:55 ` [PATCH 06/21] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-10-06 8:55 ` [PATCH 07/21] fstests: add SEMANAGE_PROG Anand Jain
2026-10-06 8:55 ` [PATCH 08/21] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-10-06 8:55 ` [PATCH 09/21] fstests: introduce helper _scratch_mkfs_uuid() Anand Jain
2026-10-06 8:55 ` [PATCH 10/21] fstests: add helpers to verify the expected f_fsid Anand Jain
2026-10-06 8:55 ` [PATCH 11/21] fstests: verify statfs f_fsid is derived from the filesystem UUID Anand Jain
2026-10-06 8:55 ` [PATCH 12/21] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-10-06 8:55 ` [PATCH 13/21] fstests: introduce _require_security_ima() helper Anand Jain
2026-10-06 8:55 ` [PATCH 14/21] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-10-06 8:55 ` [PATCH 15/21] fstests: verify exportfs file handles " Anand Jain
2026-10-06 8:55 ` [PATCH 16/21] fstests: introduce _require_metadata_uuid() helper Anand Jain
2026-10-06 8:55 ` [PATCH 17/21] fstests: add _change_metadata_uuid helper Anand Jain
2026-10-06 8:55 ` [PATCH 18/21] fstests: test UUID consistency for clones with metadata_uuid Anand Jain
2026-10-06 8:55 ` [PATCH 19/21] fstests: generic/744: use new helper _require_clone_mount() Anand Jain
2026-10-06 8:55 ` [PATCH 20/21] fstests: generic/744: migrate to _create_cloned_loop_devs() Anand Jain
2026-10-06 8:55 ` [PATCH 21/21] fstests: _create_loop_device_like_bdev() remove unused variable 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=245314b2efd616b7ecf09f74e2a775e44e10ab43.1791272793.git.asj@kernel.org \
--to=asj@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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