[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201014193551.GD16895@breakpoint.cc>
Date: Wed, 14 Oct 2020 21:35:51 +0200
From: Florian Westphal <fw@...len.de>
To: Francesco Ruggeri <fruggeri@...sta.com>
Cc: Florian Westphal <fw@...len.de>,
Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
open list <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>, coreteam@...filter.org,
netfilter-devel@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH nf v2] netfilter: conntrack: connection timeout after
re-register
Francesco Ruggeri <fruggeri@...sta.com> wrote:
> On Wed, Oct 14, 2020 at 1:23 AM Florian Westphal <fw@...len.de> wrote:
> >
> > Pablo Neira Ayuso <pablo@...filter.org> wrote:
> > > Legacy would still be flawed though.
> >
> > Its fine too, new rule blob gets handled (and match/target checkentry
> > called) before old one is dismantled.
> >
> > We only have a 0 refcount + hook unregister when rules get
> > flushed/removed explicitly.
>
> Should the patch be used in the meantime while this gets
> worked out?
I think the patch is correct, and I do NOT see a better solution.
Powered by blists - more mailing lists