From: Anand Suveer Jain <asj@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, zlang@redhat.com,
hch@infradead.org
Subject: Re: [PATCH v6 01/11] fstests: add _loop_image_create_clone() helper
Date: Mon, 8 Jun 2026 22:39:04 +0800 [thread overview]
Message-ID: <9c0989d8-202f-42ab-9347-df082c25aa72@kernel.org> (raw)
In-Reply-To: <20260529042743.GB6070@frogsfrogsfrogs>
On 29/5/26 12:27, Darrick J. Wong wrote:
> On Thu, May 28, 2026 at 12:05:32PM +0800, Anand Jain wrote:
>> 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 | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 63 insertions(+)
>>
>> diff --git a/common/rc b/common/rc
>> index 79189e7e6e94..d7e3e0bdfb1e 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -1520,6 +1520,69 @@ _scratch_resvblks()
>> esac
>> }
>>
>> +# Create a small loop image, run an optional tuning function ($2) on it,
>> +# clone it, and attach both to loop devices, returned in ($1).
>> +# Args:
>> +# $1: Nameref to return the array of allocated loop devices [base, clone].
>> +# $2: Optional callback function to tune the base filesystem before cloning.
>> +_loop_image_create_clone()
>> +{
>> + local -n _ret=$1
>
> That switch ^^ is very clever. I always wondered how one did indirect
> variables in bash.
>
>> + 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
>> +
>> + # Since we copy the block device image, we keep its size small.
>> + _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)
>
> Should this check that a loopdev actually got created?
>
Hmm, in the function _create_loop_device(), we are
calling _fail if create fails, so no need to duplicate, right?
>> + case $FSTYP in
>> + xfs)
>> + _mkfs_dev "-s size=4096" ${loop_devs[0]}
>> + ;;
>> + btrfs)
>> + _mkfs_dev ${loop_devs[0]}
>> + ;;
>> + *)
>> + _mkfs_dev ${loop_devs[0]}
>> + ;;
>> + esac
>> +
>> + # Only execute if the function argument is not empty
>> + if [ -n "$pre_clone_tune_func" ]; then
>> + $pre_clone_tune_func ${loop_devs[0]}
>> + fi
>> +
>> + sync ${loop_devs[0]}
>> + cp $img_file $img_file_clone
>> +
>> + loop_devs="$loop_devs $(_create_loop_device $img_file_clone)"
>
> local lodev="$(_create_loop_device ...)"
>
> test -z "$lodev" && _fail "second loopdev not created"
> _ret+=("$lodev")
>
> ?
If the second `_create_loop_device()` happens to fail, it will
already have called `_fail`, so "second loopdev..." won't be
used at all.
Thanks, Anand
>> +
>> + _ret=($loop_devs)
>> +}
>> +
>> +# Teardown loop devices and delete their underlying backing image files.
>> +# Accepts a list of loop device paths (e.g., /dev/loop0 /dev/loop1).
>> +_loop_image_destroy()
>> +{
>> + for d in "$@"; do
>> + # Retrieve the path of the backing file
>> + local f=$(losetup --noheadings --output BACK-FILE $d)
>> +
>> + # Detach the loop device from the backing file
>> + _destroy_loop_device "$d"
>> +
>> + # Clean up the backing disk image file
>> + [ -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
>>
>>
next prev parent reply other threads:[~2026-06-08 14:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 4:05 [PATCH v6 0/11] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-05-28 4:05 ` [PATCH v6 01/11] fstests: add _loop_image_create_clone() helper Anand Jain
2026-05-29 4:27 ` Darrick J. Wong
2026-06-08 14:39 ` Anand Suveer Jain [this message]
2026-05-28 4:05 ` [PATCH v6 02/11] fstests: add _clone_mount_option() helper Anand Jain
2026-05-29 4:28 ` Darrick J. Wong
2026-06-08 14:41 ` Anand Suveer Jain
2026-05-28 4:05 ` [PATCH v6 03/11] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-05-29 4:29 ` Darrick J. Wong
2026-05-28 4:05 ` [PATCH v6 04/11] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-05-29 4:30 ` Darrick J. Wong
2026-06-08 14:43 ` Anand Suveer Jain
2026-05-28 4:05 ` [PATCH v6 05/11] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-05-29 4:36 ` Darrick J. Wong
2026-06-08 14:45 ` Anand Suveer Jain
2026-05-28 4:05 ` [PATCH v6 06/11] fstests: verify f_fsid for " Anand Jain
2026-05-29 4:39 ` Darrick J. Wong
2026-06-08 14:59 ` Anand Suveer Jain
2026-05-28 4:05 ` [PATCH v6 07/11] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-05-28 4:05 ` [PATCH v6 08/11] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-05-28 4:05 ` [PATCH v6 09/11] fstests: verify exportfs file handles " Anand Jain
2026-05-28 4:05 ` [PATCH v6 10/11] fstests: add _change_metadata_uuid helper Anand Jain
2026-05-28 4:05 ` [PATCH v6 11/11] fstests: 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=9c0989d8-202f-42ab-9347-df082c25aa72@kernel.org \
--to=asj@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.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@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