[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrX9keVFxEZYUkKr7_dWb9Ubo9q4E2aTY_ZOWGSHyRph8g@mail.gmail.com>
Date: Mon, 20 Sep 2021 11:36:47 -0700
From: Andy Lutomirski <luto@...nel.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Thomas Weißschuh <thomas@...ch.de>,
Andy Lutomirski <luto@...nel.org>,
Christian Brauner <christian.brauner@...ntu.com>,
Linux API <linux-api@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jessica Yu <jeyu@...nel.org>
Subject: Re: [RFC] Expose request_module via syscall
On Mon, Sep 20, 2021 at 11:16 AM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Mon, Sep 20, 2021 at 04:51:19PM +0200, Thomas Weißschuh wrote:
> > > Do you mean it literally invokes /sbin/modprobe? If so, hooking this
> > > at /sbin/modprobe and calling out to the container manager seems like
> > > a decent solution.
> >
> > Yes it does. Thanks for the idea, I'll see how this works out.
>
> Would documentation guiding you in that way have helped? If so
> I welcome a patch that does just that.
If someone wants to make this classy, we should probably have the
container counterpart of a standardized paravirt interface. There
should be a way for a container to, in a runtime-agnostic way, issue
requests to its manager, and requesting a module by (name, Linux
kernel version for which that name makes sense) seems like an
excellent use of such an interface.
--Andy
>
> Luis
Powered by blists - more mailing lists