From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: "Yuezhang.Mo@sony.com" <Yuezhang.Mo@sony.com>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>
Cc: Hongbo Li <lihongbo22@huawei.com>
Subject: Re: [PATCH v1] erofs: remove the guard of showing domain_id and fsid
Date: Mon, 30 Mar 2026 16:51:34 +0800 [thread overview]
Message-ID: <c73c558d-6582-44b4-ae7f-36669e98928b@linux.alibaba.com> (raw)
In-Reply-To: <TY0PR04MB63282B4D6BAEF754115502548152A@TY0PR04MB6328.apcprd04.prod.outlook.com>
On 2026/3/30 16:48, Yuezhang.Mo@sony.com wrote:
>> On 2026/3/30 15:32, Yuezhang Mo wrote:
>>> This change fixes an issue where domain_id was not shown when
>>> CONFIG_EROFS_FS_PAGE_CACHE_SHARE is enabled, as this configuration
>>> is mutually exclusive with CONFIG_EROFS_FS_ONDEMAND.
>>>
>>> Both domain_id and fsid fields are present in struct erofs_sb_info
>>> regardless of configuration. They are not set if the configurations
>>> are not enabled, and remain NULL. Therefore, the conditional guard
>>> in erofs_show_options() are unnecessary and can be removed.
>>>
>>> Signed-off-by: Yuezhang Mo <Yuezhang.Mo@sony.com>
>>> Reviewed-by: Friendy Su <friendy.su@sony.com>
>>> Reviewed-by: Daniel Palmer <daniel.palmer@sony.com>
>>
>> `domain_id` is a user-sensitive information for the page cache
>> sharing feature (much like passwd), so it shouldn't be shown
>> in the mount option by design, and only the mounter should
>> know what it was set.
>
> Oh, this is part of the design, not a bug. Thank you for your explanation.
Yes, if you need that information in the follow-up steps,
you should keep somewhere in the userspace: but the proper
permission is needed (e.g. like /etc/shadow).
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-03-30 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:32 [PATCH v1] erofs: remove the guard of showing domain_id and fsid Yuezhang Mo
2026-03-30 7:47 ` Gao Xiang
2026-03-30 8:48 ` Yuezhang.Mo
2026-03-30 8:51 ` Gao Xiang [this message]
2026-03-30 7:48 ` Hongbo Li
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=c73c558d-6582-44b4-ae7f-36669e98928b@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=Yuezhang.Mo@sony.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.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