From: Eric Woudstra <ericwouds@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
Eric Woudstra <ericwouds@gmail.com>
Subject: [PATCH v4 nf-next 0/2] flow offload teardown when layer 2 roaming
Date: Thu, 25 Sep 2025 20:26:21 +0200 [thread overview]
Message-ID: <20250925182623.114045-1-ericwouds@gmail.com> (raw)
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
next reply other threads:[~2025-09-25 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 18:26 Eric Woudstra [this message]
2025-09-25 18:26 ` [PATCH v4 nf-next 1/2] netfilter: flow: Add bridge_vid member Eric Woudstra
2025-09-25 18:26 ` [PATCH v4 nf-next 2/2] netfilter: nf_flow_table_core: teardown direct xmit when destination changed Eric Woudstra
2025-10-02 7:55 ` Florian Westphal
2025-10-07 9:49 ` Eric Woudstra
2025-10-02 7:47 ` [PATCH v4 nf-next 0/2] flow offload teardown when layer 2 roaming Florian Westphal
2025-10-07 8:47 ` Eric Woudstra
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=20250925182623.114045-1-ericwouds@gmail.com \
--to=ericwouds@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.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;
as well as URLs for NNTP newsgroup(s).