Re: [PATCH v4 0/9] fstests: add test coverage for cloned filesystem ids
Anand Jain <[email protected]>
| Newsgroups | org.kernel.vger.fstests,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <[email protected]> |
On 12/5/26 13:37, Christoph Hellwig wrote: > This is missing a real cover letter saying what this series is trying > to archive. I should have copied from v1. See below [1] SCRATCH_DEV_POOL support for non-btrfs was dropped in v2. Instead, using the newly added helper _loop_image_create_clone(). [1] https://lore.kernel.org/fstests/[email protected]/ ----- This series adds fstests infrastructure and test cases to verify correct filesystem identity behaviour when a filesystem is cloned (e.g. via block-level copy), covering inotify, fanotify, f_fsid, libblkid, IMA, and exportfs file handles. - SCRATCH_DEV_POOL support extended to non-Btrfs filesystems - _mkfs_scratch_sized_clone() helper to create a cloned filesystem - _clone_mount_option() helper to apply per-filesystem clone mount options New tests verify: - 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 - IMA distinct identity for each cloned filesystem - exportfs file handles resolve correctly on cloned filesystems -----