[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyN8JDh76bm1VinBvrgMH5jNL6RbuFAkrH8vuYU1s9GDQ@mail.gmail.com>
Date: Fri, 9 Mar 2018 11:12:17 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: Andy Lutomirski <luto@...capital.net>,
Alexei Starovoitov <ast@...com>,
Kees Cook <keescook@...omium.org>,
Alexei Starovoitov <ast@...nel.org>,
Djalal Harouni <tixxdz@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
Daniel Borkmann <daniel@...earbox.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Luis R. Rodriguez" <mcgrof@...nel.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>
Subject: Re: [PATCH net-next] modules: allow modprobe load regular elf binaries
On Fri, Mar 9, 2018 at 10:57 AM, David Miller <davem@...emloft.net> wrote:
>
> Once the helper UMH is invoked, it runs asynchronously taking eBPF
> translation requests.
How?
Really. See my comment about mutual exclusion. The current patch is
*broken* because it doesn't handle it. Really.
Think of it this way - you may have now started *five* of those things
concurrently by mistake.
The actual module loading case never does that, because the actual
module loading case has per-module serialization that got
short-circuited.
How are you going to handle five processes doing the same setup concurrently?
Linus
Powered by blists - more mailing lists