From: Christoph Hellwig <hch@infradead.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
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 1/2] fs/super.c: introduce get_tree_bdev_by_dev()
Date: Tue, 8 Oct 2024 04:49:35 -0700 [thread overview]
Message-ID: <ZwUcT0qUp2DKOCS3@infradead.org> (raw)
In-Reply-To: <20241008095606.990466-1-hsiangkao@linux.alibaba.com>
On Tue, Oct 08, 2024 at 05:56:05PM +0800, Gao Xiang wrote:
> As Allison reported [1], currently get_tree_bdev() will store
> "Can't lookup blockdev" error message. Although it makes sense for
> pure bdev-based fses, this message may mislead users who try to use
> EROFS file-backed mounts since get_tree_nodev() is used as a fallback
> then.
>
> Add get_tree_bdev_by_dev() to specify a device number explicitly
> instead of the hardcoded fc->source as mentioned in [2], there are
> other benefits like:
> - Filesystems can have other ways to get a bdev-based sb
> in addition to the current hard-coded source path;
>
> - Pseudo-filesystems can utilize this method to generate a
> filesystem from given device numbers too.
>
> - Like get_tree_nodev(), it doesn't strictly tie to fc->source
> either.
Do you have concrete plans for any of those? If so send pointers.
Otherwise just passing a quiet flag of some form feels like a much
saner interface.
next prev parent reply other threads:[~2024-10-08 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 9:56 [PATCH 1/2] fs/super.c: introduce get_tree_bdev_by_dev() Gao Xiang
2024-10-08 9:56 ` [PATCH 2/2] erofs: use get_tree_bdev_by_dev() to avoid misleading messages Gao Xiang
2024-10-08 11:49 ` Christoph Hellwig [this message]
2024-10-08 12:10 ` [PATCH 1/2] fs/super.c: introduce get_tree_bdev_by_dev() Gao Xiang
2024-10-08 12:23 ` Christoph Hellwig
2024-10-08 12:33 ` Gao Xiang
2024-10-08 12:55 ` Christoph Hellwig
2024-10-08 13:12 ` Gao Xiang
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=ZwUcT0qUp2DKOCS3@infradead.org \
--to=hch@infradead.org \
--cc=allison.karlitskaya@redhat.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--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;
as well as URLs for NNTP newsgroup(s).