[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74e26cc0-9e72-f03b-5396-f3480921f234@fb.com>
Date: Fri, 9 Mar 2018 10:50:49 -0800
From: Alexei Starovoitov <ast@...com>
To: Andy Lutomirski <luto@...capital.net>,
Greg KH <gregkh@...uxfoundation.org>
CC: Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Alexei Starovoitov <ast@...nel.org>,
Djalal Harouni <tixxdz@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Daniel Borkmann <daniel@...earbox.net>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-team <kernel-team@...com>,
Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH net-next] modules: allow modprobe load regular elf
binaries
On 3/9/18 10:23 AM, Andy Lutomirski wrote:
>
>
>> On Mar 9, 2018, at 10:15 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>
>
>>
>> Oh, and for the record, I like Andy's proposal as well as dumping this
>> into a kernel module "blob" with the exception that this now would take
>> up unswapable memory, which isn't the nicest and is one big reason we
>> removed the in-kernel-memory firmware blobs many years ago.
>>
>
> It might not be totally crazy to back it by tmpfs.
interesting. how do you propose to do it?
Something like:
- create /umh_module_tempxxx dir
- mount tmpfs there
- copy elf into it and exec it?
Powered by blists - more mailing lists