From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <anajain.sg@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Anand Jain <asj@kernel.org>,
linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3] fix s_uuid and f_fsid consistency for cloned filesystems
Date: Thu, 5 Mar 2026 06:21:29 -0800 [thread overview]
Message-ID: <aamRaJ8PaNyxYUXN@infradead.org> (raw)
In-Reply-To: <9078e07d-5997-41f3-9991-c1f6975c768b@gmail.com>
On Thu, Mar 05, 2026 at 05:32:36PM +0800, Anand Jain wrote:
> The problem is that we won't know which filesystem is the original
> and which is the clone. Generally, the first one mounted is treated
> as the original and the following one as the clone. However, f_fsid
> should remain consistent regardless of mount order, at least for
> the duration that the block device is connected (or until a
> system reboot).
Then maybe we need to make the new sane behavior dependent on a
feature flag so that only newly created file systems use it?
next prev parent reply other threads:[~2026-03-05 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:23 [PATCH 0/3] fix s_uuid and f_fsid consistency for cloned filesystems Anand Jain
2026-02-26 14:27 ` [PATCH 1/3] btrfs: derive f_fsid from on-disk fsuuid and dev_t Anand Jain
2026-02-26 14:27 ` [PATCH 2/3] btrfs: use on-disk uuid for s_uuid in temp_fsid mounts Anand Jain
2026-02-26 14:28 ` [RFC PATCH 3/3] ext4: derive f_fsid from block device to avoid collisions Anand Jain
2026-03-04 13:28 ` [PATCH 0/3] fix s_uuid and f_fsid consistency for cloned filesystems Christoph Hellwig
2026-03-05 9:32 ` Anand Jain
2026-03-05 14:21 ` Christoph Hellwig [this message]
2026-03-22 20:31 ` Theodore Tso
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=aamRaJ8PaNyxYUXN@infradead.org \
--to=hch@infradead.org \
--cc=anajain.sg@gmail.com \
--cc=asj@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.