From: Benjamin Berg <benjamin@sipsolutions.net>
To: rrs@debian.org, linux-um@lists.infradead.org
Subject: Re: UML mount failure with Linux 6.11
Date: Thu, 31 Oct 2024 11:07:58 +0100 [thread overview]
Message-ID: <2ea3c5c4a1ecaa60414e3ed6485057ea65ca1a6e.camel@sipsolutions.net> (raw)
In-Reply-To: <857ff79f52ed50b4de8bbeec59c9820be4968183.camel@debian.org>
Hi,
Newer kernels have become more picky about that with the new mount API.
This is relevant, see the discussion about "Unknown options":
https://lwn.net/Articles/979166/
We only use hostfs for the root file system and in that case it works
well if you pass the path using "hostfs=/path" on the kernel command
line. Doing that avoids issues when remounting the file system later
on.
I suppose that currently it does not work to mount hostfs later on. No
idea what the right fix is. Maybe the host directory should be an
explicit option like "hostpath=..." or so to make it compatible with
the new mount APIs.
Benjamin
On Wed, 2024-10-30 at 13:43 +0530, Ritesh Raj Sarraf wrote:
> Hello,
>
>
> Recently I updated the UML package to Linux 6.11 in Debian. Upon it,
> it
> reports the below regression wherein UML cannot mount file systems of
> type hostfs
>
> We have it reported on the Debian bug tracker as well.
>
> * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086194
>
>
> The mount failures report as:
>
> ```
> Oct 30 05:57:41 uml systemd[1]: Mounting usr-lib-modules.mount -
> /usr/lib/modules...
> Oct 30 05:57:42 uml systemd[1]: usr-lib-modules.mount: Mount process
> exited, code=exited, status=32/n/a
> Oct 30 05:57:42 uml mount[814]: mount: /usr/lib/modules: fsconfig
> system call failed: hostfs: Unknown parameter '/usr/lib/uml/modules'.
> Oct 30 05:57:42 uml mount[814]: dmesg(1) may have more
> information after failed mount system call.
> Oct 30 05:57:42 uml systemd[1]: usr-lib-modules.mount: Failed with
> result 'exit-code'.
> Oct 30 05:57:42 uml systemd[1]: Failed to mount usr-lib-modules.mount
> - /usr/lib/modules.
>
> ```
>
> As I understand it, the issue was first seen in July, around 6.11
> rc1.
>
> *
> https://lore.kernel.org/all/CAHk-=wjH5uKPB6xrWoB8WkBMuLEJO2UsidKE1wV8XSXjAUFO8Q@mail.gmail.com/
>
>
> Thanks,
> Ritesh
>
next prev parent reply other threads:[~2024-10-31 10:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 8:13 UML mount failure with Linux 6.11 Ritesh Raj Sarraf
2024-10-31 10:07 ` Benjamin Berg [this message]
2024-11-06 11:52 ` Ritesh Raj Sarraf
2024-11-06 19:25 ` Benjamin Berg
2024-11-07 6:22 ` Hongbo Li
2024-11-07 13:09 ` Johannes Berg
2024-11-07 14:17 ` Hongbo Li
2024-11-07 14:35 ` Johannes Berg
2024-11-11 1:16 ` Hongbo Li
2024-11-12 20:10 ` Karel Zak
2024-11-13 1:23 ` Hongbo Li
2024-11-21 13:53 ` Hongbo Li
2024-11-25 17:43 ` Karel Zak
2024-11-26 13:50 ` Johannes Berg
2024-11-27 1:26 ` Hongbo Li
2024-11-27 12:02 ` Karel Zak
2024-11-27 13:15 ` Johannes Berg
2024-11-28 10:58 ` Karel Zak
2024-11-28 12:55 ` Johannes Berg
2024-11-27 13:55 ` Hongbo Li
2024-11-27 11:55 ` Karel Zak
2024-11-27 12:16 ` Geert Uytterhoeven
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=2ea3c5c4a1ecaa60414e3ed6485057ea65ca1a6e.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=rrs@debian.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