[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200318.184531.2286126098336198373.davem@davemloft.net>
Date: Wed, 18 Mar 2020 18:45:31 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: daniel@...earbox.net
Cc: netdev@...r.kernel.org, pablo@...filter.org, ast@...nel.org
Subject: Re: [PATCH net-next] netfilter: revert introduction of egress hook
From: Daniel Borkmann <daniel@...earbox.net>
Date: Wed, 18 Mar 2020 10:33:22 +0100
> 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>
Applied, this definitely needs more discussion.
Thanks Daniel.
Powered by blists - more mailing lists