From: Christoph Hellwig <hch@infradead.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Anand Jain <anajain.sg@gmail.com>, Anand Jain <asj@kernel.org>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/9] fstests: add _mkfs_scratch_clone() helper
Date: Mon, 16 Mar 2026 09:15:30 -0700 [thread overview]
Message-ID: <abgsorUy3KM8KZV5@infradead.org> (raw)
In-Reply-To: <20260314170422.a62qqwqe6agom443@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Sun, Mar 15, 2026 at 01:04:22AM +0800, Zorro Lang wrote:
> I'm concerned that testers from other filesystems might not be familiar
> with SCRATCH_DEV_POOL, as it's typically not a requirement for their
> testing. I'm not sure if they would be willing to configure and switch
> to SCRATCH_DEV_POOL, just for these few test cases. If we can avoid making
> the pool to be a hard requirement, it might be more user-friendly for other
> fs list. Welcome feedback and review points from other filesystem mailing
> lists :)
Yes, doing this using loop devices or ramdisk is going to get us much
better coverage.
next prev parent reply other threads:[~2026-03-16 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:41 [PATCH 0/9] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-02-26 14:41 ` [PATCH 1/9] fstests: allow SCRATCH_DEV_POOL for non-Btrfs filesystems Anand Jain
2026-02-26 14:41 ` [PATCH 2/9] fstests: add _mkfs_scratch_clone() helper Anand Jain
2026-03-09 19:13 ` Zorro Lang
2026-03-11 2:32 ` Anand Jain
2026-03-14 17:04 ` Zorro Lang
2026-03-16 16:15 ` Christoph Hellwig [this message]
2026-03-21 12:02 ` Anand Jain
2026-02-26 14:41 ` [PATCH 3/9] fstests: add _clone_mount_option() helper Anand Jain
2026-02-26 14:41 ` [PATCH 4/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-03-01 13:07 ` Amir Goldstein
2026-03-02 13:24 ` Anand Jain
2026-02-26 14:41 ` [PATCH 5/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-03-01 13:15 ` Amir Goldstein
2026-03-02 13:30 ` Anand Jain
2026-02-26 14:41 ` [PATCH 6/9] fstests: verify f_fsid for " Anand Jain
2026-02-26 14:41 ` [PATCH 7/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-02-26 14:41 ` [PATCH 8/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-02-26 14:41 ` [PATCH 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=abgsorUy3KM8KZV5@infradead.org \
--to=hch@infradead.org \
--cc=anajain.sg@gmail.com \
--cc=asj@kernel.org \
--cc=fstests@vger.kernel.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