Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: anzaki@gmail.com
Subject: Re: [PATCH nf-next] netfilter: flowtable: tear down flow entries with stale dst from GC
Date: Fri, 10 Jul 2026 09:45:24 +0200	[thread overview]
Message-ID: <alCjFNcjbTZpibjv@chamomile> (raw)
In-Reply-To: <20260710073610.1352167-1-pablo@netfilter.org>

On Fri, Jul 10, 2026 at 09:36:10AM +0200, Pablo Neira Ayuso wrote:
> In case of route updates, tear down flow entries with stale dst to give
> them a chance to obtain a fresh route.
> 
> This is specifically useful for hardware offloaded entries, where the
> flowtable software dataplane sees no packet, where the existing check
> for stale dst entries does not help.

Scratch this, I posted the wrong patch. Sending a v2.

> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
>  net/netfilter/nf_flow_table_core.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/net/netfilter/nf_flow_table_core.c b/net/netfilter/nf_flow_table_core.c
> index 99c5b9d671a0..61ab27de79fa 100644
> --- a/net/netfilter/nf_flow_table_core.c
> +++ b/net/netfilter/nf_flow_table_core.c
> @@ -561,6 +561,14 @@ static void nf_flow_table_extend_ct_timeout(struct nf_conn *ct)
>  	nf_ct_put(ct);
>  }
>  
> +static bool nf_flow_check_dst(struct flow_offload *flow,
> +			      enum flow_offload_tuple_dir dir)
> +{
> +	struct flow_offload_tuple *tuple = &flow->tuplehash[dir].tuple;
> +
> +	return tuple->dst_cache && dst_check(tuple->dst_cache, tuple->dst_cookie);
> +}
> +
>  static void nf_flow_offload_gc_step(struct nf_flowtable *flow_table,
>  				    struct flow_offload *flow, void *data)
>  {
> @@ -568,6 +576,8 @@ static void nf_flow_offload_gc_step(struct nf_flowtable *flow_table,
>  
>  	if (nf_flow_has_expired(flow) ||
>  	    nf_ct_is_dying(flow->ct) ||
> +	    nf_flow_check_dst(flow, FLOW_OFFLOAD_DIR_ORIGINAL) ||
> +	    nf_flow_check_dst(flow, FLOW_OFFLOAD_DIR_REPLY) ||
>  	    nf_flow_custom_gc(flow_table, flow)) {
>  		flow_offload_teardown(flow);
>  		teardown = true;
> -- 
> 2.47.3
> 
> 

      reply	other threads:[~2026-07-10  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  7:36 [PATCH nf-next] netfilter: flowtable: tear down flow entries with stale dst from GC Pablo Neira Ayuso
2026-07-10  7:45 ` Pablo Neira Ayuso [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alCjFNcjbTZpibjv@chamomile \
    --to=pablo@netfilter.org \
    --cc=anzaki@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox