From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Allison Karlitskaya <allison.karlitskaya@redhat.com>,
Chao Yu <chao@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] erofs: use get_tree_bdev_flags() to avoid misleading messages
Date: Thu, 10 Oct 2024 00:57:26 +0800 [thread overview]
Message-ID: <8ec1896f-93da-4eca-ab69-8ae9d1645181@linux.alibaba.com> (raw)
In-Reply-To: <8a40d27c-28f1-467b-9a9e-359b36ee5e33@linux.alibaba.com>
On 2024/10/9 15:37, Gao Xiang wrote:
> Hi Christoph,
>
...
>>>
>>> diff --git a/fs/erofs/super.c b/fs/erofs/super.c
>>> index 666873f745da..b89836a8760d 100644
>>> --- a/fs/erofs/super.c
>>> +++ b/fs/erofs/super.c
>>> @@ -705,7 +705,9 @@ static int erofs_fc_get_tree(struct fs_context *fc)
>>> if (IS_ENABLED(CONFIG_EROFS_FS_ONDEMAND) && sbi->fsid)
>>> return get_tree_nodev(fc, erofs_fc_fill_super);
>>> - ret = get_tree_bdev(fc, erofs_fc_fill_super);
>>> + ret = get_tree_bdev_flags(fc, erofs_fc_fill_super,
>>> + IS_ENABLED(CONFIG_EROFS_FS_BACKED_BY_FILE) ?
>>> + GET_TREE_BDEV_QUIET_LOOKUP : 0);
>>
>> Why not pass it unconditionally and provide your own more useful
>> error message at the end of the function if you could not find any
>> source?
>
> My own (potential) concern is that if CONFIG_EROFS_FS_BACKED_BY_FILE
> is off, EROFS should just behave as other pure bdev fses since I'm
> not sure if some userspace program really relies on
> "Can't lookup blockdev" behavior.
>
> .. Yet that is just my own potential worry anyway.
Many thanks all for the review... So I guess it sounds fine?
Hi Christian,
If they also look good to you, since it's a VFS change,
if possible, could you apply these two patches through
the VFS tree for this cycle? There is a redundant blank
line removal in the first patch, I guess you could help
adjust or I need to submit another version?
I also have another related fix in erofs tree to address
a syzbot issue
https://lore.kernel.org/r/20240917130803.32418-1-hsiangkao@linux.alibaba.com
but it shouldn't cause any conflict with the second
patch though..
Thanks,
Gao Xiang
>
> Thanks,
> Gao Xiang
>
next prev parent reply other threads:[~2024-10-09 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 3:31 [PATCH v2 1/2] fs/super.c: introduce get_tree_bdev_flags() Gao Xiang
2024-10-09 3:31 ` [PATCH v2 2/2] erofs: use get_tree_bdev_flags() to avoid misleading messages Gao Xiang
2024-10-09 7:31 ` Christoph Hellwig
2024-10-09 7:37 ` Gao Xiang
2024-10-09 16:57 ` Gao Xiang [this message]
2024-10-09 7:30 ` [PATCH v2 1/2] fs/super.c: introduce get_tree_bdev_flags() Christoph Hellwig
2024-10-09 15:04 ` Jan Kara
2024-10-10 9:48 ` Christian Brauner
2024-10-21 7:54 ` Gao Xiang
2024-10-21 12:27 ` Christian Brauner
2024-10-21 12:34 ` Gao Xiang
2024-10-21 12:32 ` Christian Brauner
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=8ec1896f-93da-4eca-ab69-8ae9d1645181@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=allison.karlitskaya@redhat.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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