From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <asj@kernel.org>
Cc: fstests@vger.kernel.org, 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,
djwong@kernel.org
Subject: Re: [PATCH v4 9/9] fstests: btrfs: test UUID consistency for clones with metadata_uuid
Date: Mon, 11 May 2026 22:40:00 -0700 [thread overview]
Message-ID: <agK9MC0ufkTJj-zu@infradead.org> (raw)
In-Reply-To: <d079b3f7cce446b0c5bc0762226957b960c7a3ac.1777357321.git.asj@kernel.org>
On Tue, Apr 28, 2026 at 02:42:59PM +0800, Anand Jain wrote:
> Btrfs uses the metadata_uuid superblock feature to change the on-disk UUID
> without rewriting every block header. This patch adds a sanity check to
> ensure UUID consistency when a filesystem with metadata_uuid enabled is
> cloned.
xfs does the same.
Can we abstract out the uuid change and generalize the test?
next prev parent reply other threads:[~2026-05-12 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 6:42 [PATCH v4 0/9] fstests: add test coverage for cloned filesystem ids Anand Jain
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-05-12 5:38 ` Christoph Hellwig
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
2026-05-12 5:40 ` Christoph Hellwig [this message]
2026-05-12 5:37 ` [PATCH v4 0/9] fstests: add test coverage for cloned filesystem ids Christoph Hellwig
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=agK9MC0ufkTJj-zu@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=asj@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.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