public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
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, linux-f2fs@vger.kernel.org,
	amir73il@gmail.com, zlang@redhat.com, hch@infradead.org
Subject: [PATCH v4 1/9] fstests: add _loop_image_create_clone() helper
Date: Tue, 28 Apr 2026 14:42:51 +0800	[thread overview]
Message-ID: <66f9768551f15fc448239335ae500bc86833c256.1777357321.git.asj@kernel.org> (raw)
In-Reply-To: <cover.1777357320.git.asj@kernel.org>

Introduce _loop_image_create_clone() and _loop_image_destroy() to mkfs an
image file and clone it to another image file, and attach a loop device to
them. And its destroy part.

Signed-off-by: Anand Jain <asj@kernel.org>
---
 common/rc | 47 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)

diff --git a/common/rc b/common/rc
index 9632b211b58f..754365e80dca 100644
--- a/common/rc
+++ b/common/rc
@@ -1503,6 +1503,53 @@ _scratch_resvblks()
 	esac
 }
 
+_loop_image_create_clone()
+{
+	local -n _ret=$1
+	local pre_clone_tune_func=$2
+	local img_file=$TEST_DIR/${seq}.img
+	local img_file_clone=$TEST_DIR/${seq}_clone.img
+	local size=$(_small_fs_size_mb 128) # Smallest possible
+	local loop_devs
+
+	_require_fs_space $TEST_DIR $((size * 1024))
+
+	_create_file_sized $((size * 1024 * 1024)) $img_file ||
+				_fail "Failed: Create $img_file $size"
+
+	loop_devs=$(_create_loop_device $img_file)
+	_ret=($loop_devs)
+
+	case $FSTYP in
+	xfs)
+		_mkfs_dev "-s size=4096" ${loop_devs[0]}
+		;;
+	btrfs)
+		_mkfs_dev ${loop_devs[0]}
+		;;
+	*)
+		_mkfs_dev ${loop_devs[0]}
+		;;
+	esac
+
+	($pre_clone_tune_func)
+
+	sync ${loop_devs[0]}
+	cp $img_file $img_file_clone
+
+	loop_devs="$loop_devs $(_create_loop_device $img_file_clone)"
+
+	_ret=($loop_devs)
+}
+
+_loop_image_destroy()
+{
+	for d in "$@"; do
+		local f=$(losetup --noheadings --output BACK-FILE $d)
+		_destroy_loop_device "$d"
+		[ -n "$f" ] && rm -f "$f"
+	done
+}
 
 # Repair scratch filesystem.  Returns 0 if the FS is good to go (either no
 # errors found or errors were fixed) and nonzero otherwise; also spits out
-- 
2.43.0


  reply	other threads:[~2026-04-28  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  6:42 [PATCH v4 0/9] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-04-28  6:42 ` Anand Jain [this message]
2026-04-28  6:42 ` [PATCH v4 2/9] fstests: add _clone_mount_option() helper Anand Jain
2026-04-28  6:42 ` [PATCH v4 3/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-04-28  6:42 ` [PATCH v4 4/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-04-28  6:42 ` [PATCH v4 5/9] fstests: verify f_fsid for " Anand Jain
2026-04-28  6:42 ` [PATCH v4 6/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-04-28  6:42 ` [PATCH v4 7/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-04-28  6:42 ` [PATCH v4 8/9] fstests: verify exportfs file handles " Anand Jain
2026-04-28  6:42 ` [PATCH v4 9/9] fstests: btrfs: test UUID consistency for clones with metadata_uuid 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=66f9768551f15fc448239335ae500bc86833c256.1777357321.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-f2fs@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