[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180313084835.GB8901@kroah.com>
Date: Tue, 13 Mar 2018 09:48:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alexei Starovoitov <ast@...com>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
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>,
Andy Lutomirski <luto@...capital.net>,
Kees Cook <keescook@...omium.org>,
Alexei Starovoitov <ast@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Daniel Borkmann <daniel@...earbox.net>,
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 Mon, Mar 12, 2018 at 10:22:00AM -0700, Alexei Starovoitov wrote:
> On 3/10/18 7:34 AM, Luis R. Rodriguez wrote:
> > Also,
> >
> > Alexei you never answered my questions out aliases with the umh modules.
> > Long term this important to consider.
>
> aliases always felt like a crutch to me.
> I can see an argument when they're used as 'alias pci:* foo'
> but the way it's used in networking with ip_set_* and nf-* is
> something I prefer not to ever do again.
> Definitely no aliases for bpfilter umh.
I agree, let's not do that if at all possible for these types of
binaries.
greg k-h
Powered by blists - more mailing lists