From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/9p: autoload transport modules
Date: Tue, 2 Nov 2021 16:32:21 +0100 [thread overview]
Message-ID: <3e8fcaff-6a2e-4546-87c9-a58146e02e88@t-8ch.de> (raw)
In-Reply-To: <YYFSBKXNPyIIFo7J@codewreck.org>
On 2021-11-02 23:58+0900, Dominique Martinet wrote:
> Thomas Weißschuh wrote on Tue, Nov 02, 2021 at 03:49:32PM +0100:
> > > I guess it wouldn't hurt to have 9p-tcp 9p-unix and 9p-fd aliases to the
> > > 9pnet module, but iirc these transports were more closely tied to the
> > > rest of 9pnet than the rest so it might take a while to do and I don't
> > > have much time for this right now...
> > > I'd rather not prepare for something I'll likely never get onto, so
> > > let's do this if there is progress.
> > >
> > > Of course if you'd like to have a look that'd be more than welcome :-)
> >
> > If you are still testing anyways, you could also try the attached patch.
> > (It requires the autload patch)
> >
> > It builds fine and I see no reason for it not to work.
>
> Thanks! I'll give it a spin.
>
>
> I was actually just testing the autoload one and I can't get it to work
> on my minimal VM, I guess there's a problem with the usermodhelper call
> to load module..
>
> with 9p/9pnet loaded,
> running "mount -t 9p -o trans=virtio tmp /mnt"
> request_module("9p-%s", "virtio") returns -2 (ENOENT)
Can you retry without 9p/9pnet loaded and see if they are loaded by the mount
process?
The same autoloading functionality exists for filesystems using
request_module("fs-%s") in fs/filesystems.c
If that also doesn't work it would indicate an issue with the kernel setup in general.
> Looking at the code it should be running "modprobe -q -- 9p-virtio"
> which finds the module just fine, hence my supposition usermodhelper is
> not setup correctly
>
> Do you happen to know what I need to do for it?
What is the value of CONFIG_MODPROBE_PATH?
And the contents of /proc/sys/kernel/modprobe?
> I've run out of time for today but will look tomorrow if you don't know.
>
> (And since it doesn't apparently work out of the box on these minimal
> VMs I think I'll want the trans_fd module split to sit in linux-next
> for a bit longer than a few days, so will be next merge window)
Sure.
Thomas
next prev parent reply other threads:[~2021-11-02 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 13:46 Thomas Weißschuh
2021-11-02 10:51 ` Dominique Martinet
2021-11-02 10:59 ` Thomas Weißschuh
2021-11-02 11:51 ` Dominique Martinet
2021-11-02 14:49 ` Thomas Weißschuh
2021-11-02 14:58 ` Dominique Martinet
2021-11-02 15:32 ` Thomas Weißschuh [this message]
2021-11-02 23:17 ` Dominique Martinet
2021-11-02 23:33 ` Thomas Weißschuh
2021-11-03 0:26 ` Dominique Martinet
2021-11-03 1:00 ` Dominique Martinet
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=3e8fcaff-6a2e-4546-87c9-a58146e02e88@t-8ch.de \
--to=linux@weissschuh.net \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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®