From: Anand Suveer Jain <asj@kernel.org>
To: David Sterba <dsterba@suse.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
sashal@kernel.org, linux-btrfs@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
"Macieira, Thiago" <thiago.macieira@intel.com>
Subject: Re: [PATCH 1/3] btrfs: derive f_fsid from on-disk fsuuid and dev_t
Date: Sun, 20 Sep 2026 22:13:11 +0800 [thread overview]
Message-ID: <98db278c-5302-47ed-bd3e-a47ea6e7269d@kernel.org> (raw)
In-Reply-To: <20260917172636.GW54722@suse.cz>
On 18/9/26 01:26, David Sterba wrote:
> On Wed, Sep 16, 2026 at 12:11:01AM +0800, Anand Suveer Jain wrote:
>>> I don't see the temp_fsid documented (btrfs-progs) other than in the
>>> changelogs and briefly in the sysfs file. This should be more visible as
>>> a separate feature and with the known use cases.
>>
>> Agreed. Do you think btrfs(5) is a good place to document temp_fsid?
>
> Yes, please add a section and also explain the other filesystem ids and
> how they're related. We can add references from other places using it
> (sysfs, mount and others).
Just to close the loop: the man page update was sent last week.
https://lore.kernel.org/linux-btrfs/20260918084612.ZxGVtNO9DAJfevT0EwV5BlMy-4qgIyRKK6TAZ5oNLtU@z/
David (Sterba), once commit c2a74ed0494c is reverted, based on its final
take, I will update the fstests test case on the mailing list accordingly.
next prev parent reply other threads:[~2026-09-20 14:13 UTC|newest]
Thread overview: 18+ 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-09-11 12:32 ` Dave Hansen
2026-09-11 14:51 ` Anand Suveer Jain
2026-09-11 16:07 ` Thiago Macieira
2026-09-11 18:12 ` David Woodhouse
2026-09-12 10:10 ` Anand Suveer Jain
2026-09-11 17:23 ` David Sterba
2026-09-12 10:19 ` Anand Suveer Jain
2026-09-14 13:14 ` David Sterba
2026-09-15 16:11 ` Anand Suveer Jain
2026-09-17 17:26 ` David Sterba
2026-09-20 14:13 ` Anand Suveer Jain [this message]
2026-02-26 14:27 ` [PATCH 2/3] btrfs: use on-disk uuid for s_uuid in temp_fsid mounts 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
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=98db278c-5302-47ed-bd3e-a47ea6e7269d@kernel.org \
--to=asj@kernel.org \
--cc=dave.hansen@intel.com \
--cc=dsterba@suse.com \
--cc=dwmw2@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=thiago.macieira@intel.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