From: Anand Jain <asj@kernel.org>
To: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, hch@infradead.org
Subject: [PATCH v2 0/3] fix s_uuid and f_fsid consistency for cloned filesystems
Date: Sat, 21 Mar 2026 19:55:16 +0800 [thread overview]
Message-ID: <cover.1774092915.git.asj@kernel.org> (raw)
v2:
Derive statfs::f_fsid only when using new 'nouuid'; naming matches with xfs.
v1:
btrfs:
https://lore.kernel.org/linux-btrfs/cover.1772095546.git.asj@kernel.org/
ext4:
https://lore.kernel.org/linux-ext4/e269a49eed2de23eb9f9bd7f506f0fe47696a023.1772095546.git.asj@kernel.org/
Anand Jain (3):
btrfs: use on-disk uuid for s_uuid in temp_fsid mounts
btrfs: derive f_fsid from on-disk fsuuid and dev_t
ext4: derive f_fsid from block device to avoid collisions
fs/btrfs/disk-io.c | 3 ++-
fs/btrfs/fs.h | 1 +
fs/btrfs/super.c | 35 +++++++++++++++++++++++++++++++----
fs/ext4/ext4.h | 1 +
fs/ext4/super.c | 12 ++++++++++--
5 files changed, 45 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-21 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 11:55 Anand Jain [this message]
2026-03-21 11:55 ` [PATCH v2 1/3] btrfs: use on-disk uuid for s_uuid in temp_fsid mounts Anand Jain
2026-03-21 11:55 ` [PATCH v2 2/3] btrfs: derive f_fsid from on-disk fsuuid and dev_t Anand Jain
2026-03-21 11:55 ` [PATCH v2 3/3] ext4: derive f_fsid from block device to avoid collisions Anand Jain
2026-03-23 4:16 ` Theodore Tso
2026-03-23 15:29 ` Darrick J. Wong
2026-03-23 16:44 ` Darrick J. Wong
2026-03-25 10:02 ` Andreas Dilger
2026-03-25 10:59 ` Anand Jain
2026-03-25 12:59 ` Theodore Tso
2026-03-23 15:41 ` 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=cover.1774092915.git.asj@kernel.org \
--to=asj@kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox