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 v5 0/10] fstests: add test coverage for cloned filesystem ids
Date: Thu, 21 May 2026 20:54:50 +0800 [thread overview]
Message-ID: <cover.1779367627.git.asj@kernel.org> (raw)
v5:
XFS supports metadata_uuid, I converted patch 10/10 to a generic
test. To do this, I moved the in-test helper to common/rc as
`pre_clone_tune_uuid()`.
I also verified fanotifywait with SELinux in enforcing mode and
fixed patch 4/10.
v4:
https://lore.kernel.org/fstests/cover.1777357320.git.asj@kernel.org
v3:
https://lore.kernel.org/fstests/cover.1777281778.git.asj@kernel.org
v2:
https://lore.kernel.org/fstests/cover.1774090817.git.asj@kernel.org
v1:
https://lore.kernel.org/fstests/cover.1772095513.git.asj@kernel.org
This series adds fstests infrastructure and test cases to verify correct
filesystem identity when a filesystem is cloned (block-level copy).
Test covers inotify, fanotify, f_fsid, libblkid, IMA, exportfs file handles
and libblkid tools verify with metadata_uuid.
New helpers:
- _mkfs_scratch_sized_clone() helper to create a cloned filesystem
- _clone_mount_option() helper to apply per-filesystem clone mount options
- pre_clone_tune_uuid() changes the UUID before the clone
New tests:
- inotify and fanotify events are isolated between cloned filesystems
- f_fsid is unique across cloned filesystem instances
- libblkid correctly resolves duplicate UUIDs to distinct devices
with and without metadata_uuid
- IMA distinct identity for each cloned filesystem
- exportfs file handles resolve correctly on cloned filesystems
Kernel Patches:
Requires Btrfs kernel patches for all tests to pass.
[1] https://lore.kernel.org/linux-btrfs/cover.1777281686.git.asj@kernel.org
Anand Jain (10):
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
fstests: add pre_clone_tune_uuid() healper
fstests: test UUID consistency for clones with metadata_uuid
common/config | 2 +
common/rc | 84 ++++++++++++++++++++++++++++
tests/generic/800 | 89 ++++++++++++++++++++++++++++++
tests/generic/800.out | 7 +++
tests/generic/801 | 125 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/801.out | 7 +++
tests/generic/802 | 62 +++++++++++++++++++++
tests/generic/802.out | 7 +++
tests/generic/803 | 76 +++++++++++++++++++++++++
tests/generic/803.out | 19 +++++++
tests/generic/804 | 103 ++++++++++++++++++++++++++++++++++
tests/generic/804.out | 10 ++++
tests/generic/805 | 73 ++++++++++++++++++++++++
tests/generic/805.out | 2 +
tests/generic/806 | 78 ++++++++++++++++++++++++++
tests/generic/806.out | 19 +++++++
16 files changed, 763 insertions(+)
create mode 100644 tests/generic/800
create mode 100644 tests/generic/800.out
create mode 100644 tests/generic/801
create mode 100644 tests/generic/801.out
create mode 100644 tests/generic/802
create mode 100644 tests/generic/802.out
create mode 100644 tests/generic/803
create mode 100644 tests/generic/803.out
create mode 100644 tests/generic/804
create mode 100644 tests/generic/804.out
create mode 100644 tests/generic/805
create mode 100644 tests/generic/805.out
create mode 100644 tests/generic/806
create mode 100644 tests/generic/806.out
--
2.43.0
next reply other threads:[~2026-05-21 13:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 12:54 Anand Jain [this message]
2026-05-21 12:54 ` [PATCH v5 01/10] fstests: add _loop_image_create_clone() helper Anand Jain
2026-05-25 7:07 ` Christoph Hellwig
2026-05-21 12:54 ` [PATCH v5 02/10] fstests: add _clone_mount_option() helper Anand Jain
2026-05-25 7:07 ` Christoph Hellwig
2026-05-21 12:54 ` [PATCH v5 03/10] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-05-25 7:09 ` Christoph Hellwig
2026-05-25 8:35 ` Anand Jain
2026-05-21 12:54 ` [PATCH v5 04/10] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-05-25 7:11 ` Christoph Hellwig
2026-05-25 8:20 ` Anand Jain
2026-05-21 12:54 ` [PATCH v5 05/10] fstests: verify f_fsid for " Anand Jain
2026-05-25 7:13 ` Christoph Hellwig
2026-05-21 12:54 ` [PATCH v5 06/10] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-05-21 12:54 ` [PATCH v5 07/10] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-05-21 12:54 ` [PATCH v5 08/10] fstests: verify exportfs file handles " Anand Jain
2026-05-21 12:54 ` [PATCH v5 09/10] fstests: add pre_clone_tune_uuid() healper Anand Jain
2026-05-21 13:10 ` Anand Jain
2026-05-25 7:14 ` Christoph Hellwig
2026-05-25 7:31 ` Anand Jain
2026-05-25 7:48 ` Christoph Hellwig
2026-05-21 12:55 ` [PATCH v5 10/10] 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=cover.1779367627.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