From: Andy Lutomirski <luto@kernel.org>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: "Luis Chamberlain" <mcgrof@kernel.org>,
"Thomas Weißschuh" <thomas@t-8ch.de>,
"Linux API" <linux-api@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jessica Yu" <jeyu@kernel.org>
Subject: Re: [RFC] Expose request_module via syscall
Date: Fri, 24 Sep 2021 16:04:39 -0700 [thread overview]
Message-ID: <b7390542-ea4a-de12-7567-734f6dbf488d@kernel.org> (raw)
In-Reply-To: <20210924131939.4jaou665fodiziml@wittgenstein>
On 9/24/21 06:19, Christian Brauner wrote:
> On Wed, Sep 22, 2021 at 01:06:49PM -0700, Andy Lutomirski wrote:
> I just meant that the programs in the container can see the modules
> available on the host. Simplest thing could be bind-mounting in the
> host's module folder with suitable protection (locked read-only mount).
> But yeah, it can likely be as simple as allowing it to ask for a module
> and not bother telling it about what is available.
>
If the container gets to see host modules, interesting races when
containers are migrated CRIU-style will result.
next prev parent reply other threads:[~2021-09-24 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 15:49 [RFC] Expose request_module via syscall Thomas Weißschuh
2021-09-15 16:02 ` Greg KH
2021-09-15 16:28 ` Thomas Weißschuh
2021-09-15 16:47 ` Andy Lutomirski
2021-09-16 9:27 ` Christian Brauner
2021-09-18 18:47 ` Andy Lutomirski
2021-09-19 7:56 ` Thomas Weißschuh
2021-09-19 14:37 ` Andy Lutomirski
2021-09-20 14:51 ` Thomas Weißschuh
2021-09-20 16:59 ` Luis Chamberlain
2021-09-20 18:36 ` Andy Lutomirski
2021-09-22 12:25 ` Christian Brauner
2021-09-22 15:34 ` Andy Lutomirski
2021-09-22 15:52 ` Christian Brauner
2021-09-22 20:06 ` Andy Lutomirski
2021-09-24 13:19 ` Christian Brauner
2021-09-24 23:04 ` Andy Lutomirski [this message]
2021-10-24 9:38 ` Thomas Weißschuh
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=b7390542-ea4a-de12-7567-734f6dbf488d@kernel.org \
--to=luto@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=jeyu@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=thomas@t-8ch.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.