From: Anand Suveer Jain <asj@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, zlang@redhat.com,
hch@infradead.org
Subject: Re: [PATCH v7 06/11] fstests: verify f_fsid for cloned filesystems
Date: Wed, 22 Jul 2026 07:21:15 +0800 [thread overview]
Message-ID: <18d569b9-dbea-448c-8b3d-56de32c0d6ef@kernel.org> (raw)
In-Reply-To: <20260721225703.GZ7380@frogsfrogsfrogs>
>>> just in case there *are* programs foolish enough to
>>> use (fsid,ino) as a uniqueness check.
>>
>> On the other hand, if a program needs a unique ID, do we currently have
>> any way to get one?
>
> I don't think there is a way to get a globally unique identifier for a
> filesystem image except for the meta_uuid filesystems, and even then
> only if the volume manager resets the user-visible uuid every time it
> makes a clone and nobody runs a duplicator.
Yeah, interesting problem to solve though.
Do you have any further code review comments on this test case?
Thanks.
next prev parent reply other threads:[~2026-07-21 23:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 11:20 [PATCH v7 0/11] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-06-17 11:20 ` [PATCH v7 01/11] fstests: add _loop_image_create_clone() helper Anand Jain
2026-07-01 17:07 ` Darrick J. Wong
2026-07-21 22:38 ` Anand Suveer Jain
2026-06-17 11:20 ` [PATCH v7 02/11] fstests: add _clone_mount_option() helper Anand Jain
2026-06-17 11:20 ` [PATCH v7 03/11] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-06-17 11:20 ` [PATCH v7 04/11] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-07-01 17:11 ` Darrick J. Wong
2026-07-21 22:37 ` Anand Suveer Jain
2026-06-17 11:20 ` [PATCH v7 05/11] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-07-01 17:12 ` Darrick J. Wong
2026-07-21 22:36 ` Anand Suveer Jain
2026-06-17 11:20 ` [PATCH v7 06/11] fstests: verify f_fsid for " Anand Jain
2026-07-01 17:33 ` Darrick J. Wong
2026-07-21 22:36 ` Anand Suveer Jain
2026-07-21 22:57 ` Darrick J. Wong
2026-07-21 23:21 ` Anand Suveer Jain [this message]
2026-07-21 23:25 ` Darrick J. Wong
2026-06-17 11:20 ` [PATCH v7 07/11] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-06-17 11:20 ` [PATCH v7 08/11] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-06-17 11:20 ` [PATCH v7 09/11] fstests: verify exportfs file handles " Anand Jain
2026-06-17 11:20 ` [PATCH v7 10/11] fstests: add _change_metadata_uuid helper Anand Jain
2026-06-17 11:20 ` [PATCH v7 11/11] 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=18d569b9-dbea-448c-8b3d-56de32c0d6ef@kernel.org \
--to=asj@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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