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 v4 0/9] fstests: add test coverage for cloned filesystem ids
Date: Tue, 28 Apr 2026 14:42:50 +0800 [thread overview]
Message-ID: <cover.1777357320.git.asj@kernel.org> (raw)
v4:
In _loop_image_create_clone() (Patch 1/9):
. Added _require_fs_space $TEST_DIR $((size * 1024)).
. Switched to the _create_file_sized() helper.
. Used the loop device in mkfs instead of the image file directly.
. Added a sync on the loop device before copying to ensure consistency.
For test cases (Patches 3/9 to 9/9):
. Added _require_block_device $TEST_DEV.
For test case (Patch 4/9):
. Removed the ext4 patch reference in _fixed_by_kernel_commit since
that part of the plan was dropped.
v3:
https://lore.kernel.org/fstests/cover.1777281778.git.asj@kernel.org
Anand Jain (9):
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: btrfs: test UUID consistency for clones with metadata_uuid
common/config | 2 +
common/rc | 61 +++++++++++++++++++++++
tests/btrfs/348 | 92 ++++++++++++++++++++++++++++++++++
tests/btrfs/348.out | 19 +++++++
tests/generic/800 | 89 +++++++++++++++++++++++++++++++++
tests/generic/800.out | 7 +++
tests/generic/801 | 113 ++++++++++++++++++++++++++++++++++++++++++
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 +
16 files changed, 742 insertions(+)
create mode 100644 tests/btrfs/348
create mode 100644 tests/btrfs/348.out
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
--
2.43.0
next reply other threads:[~2026-04-28 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 6:42 Anand Jain [this message]
2026-04-28 6:42 ` [PATCH v4 1/9] fstests: add _loop_image_create_clone() helper Anand Jain
2026-04-28 6:42 ` [PATCH v4 2/9] fstests: add _clone_mount_option() helper Anand Jain
2026-04-28 6:42 ` [PATCH v4 3/9] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-04-28 6:42 ` [PATCH v4 4/9] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-04-28 6:42 ` [PATCH v4 5/9] fstests: verify f_fsid for " Anand Jain
2026-04-28 6:42 ` [PATCH v4 6/9] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-04-28 6:42 ` [PATCH v4 7/9] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-04-28 6:42 ` [PATCH v4 8/9] fstests: verify exportfs file handles " Anand Jain
2026-04-28 6:42 ` [PATCH v4 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=cover.1777357320.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