From: Christian Brauner <brauner@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: "Maciej Żenczykowski" <maze@google.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Kernel hackers" <linux-kernel@vger.kernel.org>,
"Patrick Rohr" <prohr@google.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: UML/hostfs - mount failure at tip of tree
Date: Fri, 26 Jul 2024 09:41:02 +0200 [thread overview]
Message-ID: <20240726-burggraben-zugluft-351cfa07d2de@brauner> (raw)
In-Reply-To: <4a8ae74e-2f90-4da8-9511-325ca6f67aa6@huawei.com>
On Wed, Jul 24, 2024 at 05:49:16PM GMT, Hongbo Li wrote:
>
>
> On 2024/7/24 11:59, Maciej Żenczykowski wrote:
> > On Tue, Jul 23, 2024 at 7:55 PM Maciej Żenczykowski <maze@google.com> wrote:
> > >
> > > On Tue, Jul 23, 2024 at 7:22 PM Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > >
> > > > On Tue, 23 Jul 2024 at 18:35, Hongbo Li <lihongbo22@huawei.com> wrote:
> > > > >
> > > > > I apologize for causing this issue. I am currently tracking it down. If
> > > > > reverting this can solve the problem, you can revert it first.
> > > >
> > > > I don't get the feeling that this is _so_ urgent that it needs to be
> > > > reverted immediately - let's give it at least a few days and see if
> > > > you (or somebody else) figures out the bug.
> > > >
> > > > Maciej - if you can verify that folio conversion fix suggestion of
> > > > mine (or alternatively report that it doesn't help and I was barking
> > > > up the wrong tree), that would be great.
> > >
> > > That appears to fix the folio patch indeed (ie. I no longer need to revert it).
> > >
> > > The tests are still super unhappy, but I've yet to fix our tests very
> > > broken netlink parser for changes that released in 6.10, so that may
> > > be unrelated ;-)
> >
> > +++ fs/hostfs/hostfs_kern.c:
> > static int hostfs_fill_super(struct super_block *sb, struct fs_context *fc)
> > {
> > struct hostfs_fs_info *fsi = sb->s_fs_info;
> > - const char *host_root = fc->source;
> > + const char *host_root = "/";
> >
> This doesn't work in case where the host directory is designated (such as
> mount -t hostfs hostfs -o /home /host).
>
> I can fix this by the following patch, the root cause of this issue is the
> incorrect parsing of the host directory. The original mount path will use
> `parse_monolithic` to parse the host directory. For the new mount api, it
> use `parse_param` directly. So we should call `fsconfig(fd,
> FSCONFIG_SET_STRING, "hostfs", "xxx", 0)` to mount the hostfs(I think may be
> we should add hostfs as the key for host directory.). This may need
> Christian's reviews.:
I see you sent the patch. I looked at it yesterday but didn't really dig
into it. Let me go do that now. I'll have a pr ready for Linus latest
tomorrow.
next prev parent reply other threads:[~2024-07-26 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 22:33 Maciej Żenczykowski
2024-07-24 1:14 ` Linus Torvalds
2024-07-24 1:34 ` Hongbo Li
2024-07-24 2:22 ` Linus Torvalds
2024-07-24 2:55 ` Maciej Żenczykowski
2024-07-24 3:59 ` Maciej Żenczykowski
2024-07-24 9:49 ` Hongbo Li
2024-07-26 7:41 ` Christian Brauner [this message]
2024-07-26 7:52 ` Christian Brauner
2024-07-26 8:36 ` Hongbo Li
2024-07-24 2:54 ` 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=20240726-burggraben-zugluft-351cfa07d2de@brauner \
--to=brauner@kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@google.com \
--cc=prohr@google.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®