From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Linux API <linux-api@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Jessica Yu <jeyu@kernel.org>
Subject: Re: [RFC] Expose request_module via syscall
Date: Sun, 24 Oct 2021 11:38:19 +0200 [thread overview]
Message-ID: <97e88a06-4dfc-485c-b562-bed2a8e4b1b8@t-8ch.de> (raw)
In-Reply-To: <6eff0e8a-4965-437d-9273-1d9d73892e1a@t-8ch.de>
On 2021-09-19 09:56+0200, Thomas Weißschuh wrote:
> On 2021-09-18T11:47-0700, Andy Lutomirski wrote:
> > But I admit I’m a bit confused. What exactly is the container doing that causes the container’s copy of modprobe to be called?
>
> The container is running an instance of the docker daemon in swarm mode.
> That needs the "ip_vs" module (amongst others) and explicitly tries to load it
> via modprobe.
If somebody stumbles upon this specific issue:
The "ip_vs" module will be autoloaded in future kernel versions with
https://lore.kernel.org/lkml/20211021130255.4177-1-linux@weissschuh.net/
applied.
> > > If so the seccomp notifier can be used to intercept this system call for
> > > the container and verify the module against an allowlist similar to how
> > > we currently handle mount.
> > >
> > > Christian
prev parent reply other threads:[~2021-10-24 9:38 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
2021-10-24 9:38 ` Thomas Weißschuh [this message]
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=97e88a06-4dfc-485c-b562-bed2a8e4b1b8@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=christian.brauner@ubuntu.com \
--cc=jeyu@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mcgrof@kernel.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;
as well as URLs for NNTP newsgroup(s).