Linux EXT4 FS development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Anand Suveer 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-devel@lists.sourceforge.net, zlang@redhat.com,
	hch@infradead.org
Subject: Re: [PATCH v7 06/11] fstests: verify f_fsid for cloned filesystems
Date: Tue, 21 Jul 2026 15:57:03 -0700	[thread overview]
Message-ID: <20260721225703.GZ7380@frogsfrogsfrogs> (raw)
In-Reply-To: <328de723-6f9c-4f09-a68a-da24d49300d5@kernel.org>

On Wed, Jul 22, 2026 at 06:36:13AM +0800, Anand Suveer Jain wrote:
> 
> 
> > This is where I continue getting stuck on this patchset -- fsid is so
> > poorly defined that I don't think the rest of these fsid tests make
> > sense at all.  Nobody mandates that fsid is persistent or stable across
> > remounts.  Nobody even mandates that two cloned filesystems don't have
> > the same fsid value.
> > 
> > The statfs manpage says:
> > 
> > "Nobody knows what f_fsid is supposed to contain (but see below)"
> > 
> > and then:
> > 
> > "The general idea is that f_fsid contains some random stuff such that
> > the pair (f_fsid,ino) uniquely determines a file."
> 
> Which is exactly why we need fstests guardrails.
> Keeps filesystem's implementation consistent across kernel versions.
> Embarrassingly, I introduced a bug around this that is now fixed.
> The commit IDs are in the test cases.
> Thus motivation for this fstests patch.
> 
> > Based on that very weak statement, at most it might make sense to check
> > that two separate and simultaneously mounted filesystems don't end up
> > with the same fsid 
> 
> Yes, for xfs, btrfs and f2fs. However for ext4 cloned filesystems can
> share the same fsid and ino because the images are identical.
> It is then up to the usecase to change the UUID for either filesystem if
> it gets modified.
> Commit ("fstests: add _require_unique_f_fsid() helper") captures this,
> and the link in that commit includes the discussion.
> 
> > 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.

--D

> Thanks, Anand
> 
> 
> 

  reply	other threads:[~2026-07-21 22:57 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 [this message]
2026-07-21 23:21         ` Anand Suveer Jain
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=20260721225703.GZ7380@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=asj@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