[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250925182623.114045-1-ericwouds@gmail.com>
Date: Thu, 25 Sep 2025 20:26:21 +0200
From: Eric Woudstra <ericwouds@...il.com>
To: Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Florian Westphal <fw@...len.de>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Nikolay Aleksandrov <razor@...ckwall.org>
Cc: netfilter-devel@...r.kernel.org,
netdev@...r.kernel.org,
Eric Woudstra <ericwouds@...il.com>
Subject: [PATCH v4 nf-next 0/2] flow offload teardown when layer 2 roaming
This patch-set can be reviewed separately from my submissions concerning
the bridge-fastpath.
In case of a bridge in the forward-fastpath or bridge-fastpath the fdb is
used to create the tuple. In case of roaming at layer 2 level, for example
802.11r, the destination device is changed in the fdb. The destination
device of a direct transmitting tuple is no longer valid and traffic is
send to the wrong destination. Also the hardware offloaded fastpath is not
valid anymore.
This flowentry needs to be torn down asap.
Changes in v4:
- Removed patch "don't follow fastpath when marked teardown".
- Use a work queue to process the event.
Changes in v3:
- static nf_flow_table_switchdev_nb.
Changes in v2:
- Unchanged, only tags RFC net-next to PATCH nf-next.
Eric Woudstra (2):
netfilter: flow: Add bridge_vid member
netfilter: nf_flow_table_core: teardown direct xmit when destination
changed
include/net/netfilter/nf_flow_table.h | 2 +
net/netfilter/nf_flow_table_core.c | 89 +++++++++++++++++++++++++++
net/netfilter/nft_flow_offload.c | 3 +
3 files changed, 94 insertions(+)
--
2.50.0
Powered by blists - more mailing lists