[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbc7ef7a-83fe-67ab-3637-c064edf63cb8@fb.com>
Date: Thu, 22 Mar 2018 15:21:33 -0700
From: Alexei Starovoitov <ast@...com>
To: Andy Lutomirski <luto@...nel.org>,
"Luis R. Rodriguez" <mcgrof@...nel.org>
CC: Jessica Yu <jeyu@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Djalal Harouni <tixxdz@...il.com>,
David Miller <davem@...emloft.net>,
Kees Cook <keescook@...omium.org>,
Alexei Starovoitov <ast@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Daniel Borkmann <daniel@...earbox.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Network Development <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kernel-team <kernel-team@...com>,
Linux API <linux-api@...r.kernel.org>,
Michal Hocko <mhocko@...nel.org>,
Hannes Reinecke <hare@...e.com>, <werner@...e.com>
Subject: Re: [PATCH net-next] modules: allow modprobe load regular elf
binaries
On 3/22/18 3:15 PM, Andy Lutomirski wrote:
> On Thu, Mar 22, 2018 at 8:54 PM, Luis R. Rodriguez <mcgrof@...nel.org> wrote:
>> If we can ensure that these usermode modules don't take *any time at all* on
>> their init *from the start*, it would be wonderful and we'd end up avoiding
>> some really odd corner case issues later.
>>
>
> I don't see why this issue needs to exist at all for the new stuff.
> After all, the new things aren't usermode modules per se. They're
> regular kernel code (modular or otherwise) that loads a usermode
> helper. All we need to do is to make sure that, if this is
> distributed as a module, that it's init routine doesn't wait for a
> long time, right?
I've implemented all of the previous suggestions and
now there are zero changes to kernel/module.c
I still need to finish tracpoint stuff first and polish umh code a bit
before sending new version.
Let's hold on this thread until then.
Powered by blists - more mailing lists