From: Anand Jain <anajain.sg@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>, Anand Jain <asj@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs@vger.kernel.org, zlang@redhat.com, hch@infradead.org
Subject: Re: [PATCH v3 1/9] fstests: add _loop_image_create_clone() helper
Date: Tue, 28 Apr 2026 14:42:51 +0800 [thread overview]
Message-ID: <71447b65-0390-47a6-b0ec-7727a3009256@gmail.com> (raw)
In-Reply-To: <CAOQ4uxjEcHiqzB+JrnzDExMcBuTbLaPT5qQcEDX0GO0TX7hp=g@mail.gmail.com>
On 28/4/26 02:31, Amir Goldstein wrote:
> On Mon, Apr 27, 2026 at 12:19 PM Anand Jain <asj@kernel.org> 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 | 44 ++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 44 insertions(+)
>>
>> diff --git a/common/rc b/common/rc
>> index 9632b211b58f..0e7b7eb1d98f 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -1503,6 +1503,50 @@ _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
>> +
>> + size=$((size * 1024 * 1024))
>> + $XFS_IO_PROG -f -c "truncate $size" $img_file
>> +
>> + loop_devs=$(_create_loop_device $img_file)
>> + _ret=($loop_devs)
>> +
>> + case $FSTYP in
>> + xfs)
>> + _mkfs_dev "-s size=4096" $img_file
>> + ;;
>> + btrfs)
>> + _mkfs_dev $img_file
>> + ;;
>> + *)
>> + _mkfs_dev $img_file
>
> You making a wrong assumption that FSTYP can format the loop devices
>
> You should add _require_block_device $SCRATCH_DEV
> to all your tests or maybe nicer, add:
>
> _require_loop_mountable which requires loop and block dev fs
> and use this requirement instead of just _require_loop in all tests.
>
Thanks. I've fixed this in v4 by adding
_require_block_device $TEST_DEV
Since SCRATCH_DEV is not required.
I didn't create a new _require_loop_mountable() helper.
Both _require_loop() and _require_block_device() are
used both together across other existing tests;
I prefer not to deviate into cleaning that up in this
patch set.
v4 is in the ML for rvb.
Thanks, Anand
> Thanks,
> Amir.
next prev parent reply other threads:[~2026-04-28 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 10:19 [PATCH v3 0/9] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-04-27 10:19 ` [PATCH v3 1/9] fstests: add _loop_image_create_clone() helper Anand Jain
2026-04-27 18:31 ` Amir Goldstein
2026-04-28 6:42 ` Anand Jain [this message]
2026-04-27 10:19 ` [PATCH v3 2/9] fstests: add _clone_mount_option() helper Anand Jain
2026-04-27 10:19 ` [PATCH v3 3/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-04-27 17:15 ` Amir Goldstein
2026-04-27 10:19 ` [PATCH v3 4/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-04-27 18:32 ` Amir Goldstein
2026-04-27 10:19 ` [PATCH v3 5/9] fstests: verify f_fsid for " Anand Jain
2026-04-27 10:19 ` [PATCH v3 6/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-04-27 10:19 ` [PATCH v3 7/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-04-27 10:19 ` [PATCH v3 8/9] fstests: verify exportfs file handles " Anand Jain
2026-04-27 10:19 ` [PATCH v3 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=71447b65-0390-47a6-b0ec-7727a3009256@gmail.com \
--to=anajain.sg@gmail.com \
--cc=amir73il@gmail.com \
--cc=asj@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@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