[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97a81974-5063-ed3d-8ad4-9f7ff3aa0908@iogearbox.net>
Date: Wed, 18 Mar 2020 10:41:30 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
Alexei Starovoitov <ast@...nel.org>
Subject: Re: [PATCH net-next] netfilter: revert introduction of egress hook
On 3/18/20 10:36 AM, Pablo Neira Ayuso wrote:
> On Wed, Mar 18, 2020 at 10:33:22AM +0100, Daniel Borkmann wrote:
>> This reverts the following commits:
>>
>> 8537f78647c0 ("netfilter: Introduce egress hook")
>> 5418d3881e1f ("netfilter: Generalize ingress hook")
>> b030f194aed2 ("netfilter: Rename ingress hook include file")
>>
>> From the discussion in [0], the author's main motivation to add a hook
>> in fast path is for an out of tree kernel module, which is a red flag
>> to begin with. Other mentioned potential use cases like NAT{64,46}
>> is on future extensions w/o concrete code in the tree yet. Revert as
>> suggested [1] given the weak justification to add more hooks to critical
>> fast-path.
>>
>> [0] https://lore.kernel.org/netdev/cover.1583927267.git.lukas@wunner.de/
>> [1] https://lore.kernel.org/netdev/20200318.011152.72770718915606186.davem@davemloft.net/
>>
>> Signed-off-by: Daniel Borkmann <daniel@...earbox.net>
>
> Nacked-by: Pablo Neira Ayuso <pablo@...filter.org>
>
> Daniel, you must be really worried about achieving your goals if you
> have to do politics to block stuff.
Looks like this is your only rationale technical argument you can come
up with?
Thanks,
Daniel
Powered by blists - more mailing lists