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, amir73il@gmail.com, zlang@redhat.com,
hch@infradead.org
Subject: [PATCH v2 0/9] fstests: add test coverage for cloned filesystem ids
Date: Sat, 21 Mar 2026 19:58:21 +0800 [thread overview]
Message-ID: <cover.1774090817.git.asj@kernel.org> (raw)
v2:
- Add new helper _require_nouuid_mountopt() inline with the btrfs and
ext4 nouuid mount option, matching xfs.
- Clean up background processes in the _cleanup().
- Use fsnotifywait(1) instead of a local tool.
- Drop the use of SCRATCH_DEV_POOL for generic test cases to keep the
existing xfs/ext4 test environment compatible for better coverage.
v1:
https://lore.kernel.org/fstests/cover.1772095513.git.asj@kernel.org
Anand Jain (9):
fstests: add _require_nouuid_mountopt() helper
fstests: add _loop_image_create_clone() helper
fstests: add _clone_mount_option() helper
fstests: add test for inotify isolation on cloned devices
fstests: verify fanotify isolation on cloned filesystems
fstests: verify f_fsid for cloned filesystems
fstests: verify libblkid resolution of duplicate UUIDs
fstests: verify IMA isolation on cloned filesystems
fstests: verify exportfs file handles on cloned filesystems
common/config | 2 +
common/rc | 74 +++++++++++++++++++++++++++
tests/generic/790 | 89 ++++++++++++++++++++++++++++++++
tests/generic/790.out | 7 +++
tests/generic/791 | 116 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/791.out | 7 +++
tests/generic/792 | 62 ++++++++++++++++++++++
tests/generic/792.out | 7 +++
tests/generic/793 | 76 +++++++++++++++++++++++++++
tests/generic/793.out | 19 +++++++
tests/generic/794 | 103 +++++++++++++++++++++++++++++++++++++
tests/generic/794.out | 10 ++++
tests/generic/795 | 73 ++++++++++++++++++++++++++
tests/generic/795.out | 2 +
14 files changed, 647 insertions(+)
create mode 100644 tests/generic/790
create mode 100644 tests/generic/790.out
create mode 100644 tests/generic/791
create mode 100644 tests/generic/791.out
create mode 100644 tests/generic/792
create mode 100644 tests/generic/792.out
create mode 100644 tests/generic/793
create mode 100644 tests/generic/793.out
create mode 100644 tests/generic/794
create mode 100644 tests/generic/794.out
create mode 100644 tests/generic/795
create mode 100644 tests/generic/795.out
--
2.43.0
next reply other threads:[~2026-03-21 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 11:58 Anand Jain [this message]
2026-03-21 11:58 ` [PATCH v2 1/9] fstests: add _require_nouuid_mountopt() helper Anand Jain
2026-03-21 11:58 ` [PATCH v2 2/9] fstests: add _loop_image_create_clone() helper Anand Jain
2026-03-21 11:58 ` [PATCH v2 3/9] fstests: add _clone_mount_option() helper Anand Jain
2026-03-21 11:58 ` [PATCH v2 4/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-03-21 11:58 ` [PATCH v2 5/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-03-21 11:58 ` [PATCH v2 6/9] fstests: verify f_fsid for " Anand Jain
2026-03-21 11:58 ` [PATCH v2 7/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-03-21 11:58 ` [PATCH v2 8/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-03-21 11:58 ` [PATCH v2 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=cover.1774090817.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-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