From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, horms@kernel.org, fw@strlen.de, ja@ssi.bg
Subject: Re: [PATCH net-next 01/13] netfilter: flowtable: do not hw offload flows in teardown state
Date: Tue, 17 Nov 2026 11:20:07 +0000 [thread overview]
Message-ID: <179491440753.514086.6452925778003138386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116001612.2806263-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Mon, 16 Nov 2026 01:16:00 +0100 you wrote:
> Sashiko reports that refreshing hw offload from packet path is racy
> since the flow might be already torn down.
>
> Since commit 7c549fb7eecd ("netfilter: flowtable: generalize pending
> status bit"), GC skips flow entries that are still pending to be
> offloaded. Let's just check for the teardown status bit after the
> pending bit is set on to address this race.
>
> [...]
Here is the summary with links:
- [net-next,01/13] netfilter: flowtable: do not hw offload flows in teardown state
https://git.kernel.org/netdev/net-next/c/0abb54363974
- [net-next,02/13] netfilter: flowtable: retrieve stats on flow deletion
https://git.kernel.org/netdev/net-next/c/2785eca574b0
- [net-next,03/13] net: ethernet: mtk_ppe: update stats on flow deletion
https://git.kernel.org/netdev/net-next/c/272435e43f1c
- [net-next,04/13] net: airoha: update stats on flow deletion
https://git.kernel.org/netdev/net-next/c/0602fe6ca35c
- [net-next,05/13] netfilter: xt_time: fix monthday computation for dates past 2039
https://git.kernel.org/netdev/net-next/c/71d4a4199524
- [net-next,06/13] netfilter: nft_flow_offload: do not offload multicast
https://git.kernel.org/netdev/net-next/c/b0ca1ef87626
- [net-next,07/13] netfilter: flowtable: purge entries immediately when destroying the flowtable
https://git.kernel.org/netdev/net-next/c/1ba460c8e20b
- [net-next,08/13] selftests: netfilter: nf_queue: drop the no-op loop initializer
https://git.kernel.org/netdev/net-next/c/f1eaa9155e69
- [net-next,09/13] netfilter: flowtable: do not scrub as crossing netns
https://git.kernel.org/netdev/net-next/c/4733af7f19e7
- [net-next,10/13] netfilter: flowtable: tunnel device poisons h_source of fast-path frames
https://git.kernel.org/netdev/net-next/c/ada5902116b4
- [net-next,11/13] netfilter: flowtable: do not clear the offload bit twice
https://git.kernel.org/netdev/net-next/c/8147f6e61e16
- [net-next,12/13] netfilter: nfnetlink_queue: make skb writable before writing NFQA_L2HDR
https://git.kernel.org/netdev/net-next/c/3abad1970ab4
- [net-next,13/13] selftests: netfilter: add UDP flowtable offload test
https://git.kernel.org/netdev/net-next/c/03b7948d634a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-17 11:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 0:15 [PATCH net-next,v2 00/13] Netfilter updates for net-next Pablo Neira Ayuso
2026-11-16 0:16 ` [PATCH net-next 01/13] netfilter: flowtable: do not hw offload flows in teardown state Pablo Neira Ayuso
2026-11-16 0:23 ` netdev-bot+sinfo
2026-11-16 0:27 ` Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-17 9:40 ` Paolo Abeni
2026-11-17 10:26 ` Pablo Neira Ayuso
2026-11-17 11:20 ` patchwork-bot+netdevbpf [this message]
2026-11-16 0:16 ` [PATCH net-next 02/13] netfilter: flowtable: retrieve stats on flow deletion Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 03/13] net: ethernet: mtk_ppe: update " Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 04/13] net: airoha: " Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 05/13] netfilter: xt_time: fix monthday computation for dates past 2039 Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 06/13] netfilter: nft_flow_offload: do not offload multicast Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 07/13] netfilter: flowtable: purge entries immediately when destroying the flowtable Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 08/13] selftests: netfilter: nf_queue: drop the no-op loop initializer Pablo Neira Ayuso
2026-11-16 0:16 ` [PATCH net-next 09/13] netfilter: flowtable: do not scrub as crossing netns Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
2026-11-16 0:16 ` [PATCH net-next 10/13] netfilter: flowtable: tunnel device poisons h_source of fast-path frames Pablo Neira Ayuso
2026-11-16 0:16 ` [PATCH net-next 11/13] netfilter: flowtable: do not clear the offload bit twice Pablo Neira Ayuso
2026-11-16 0:16 ` [PATCH net-next 12/13] netfilter: nfnetlink_queue: make skb writable before writing NFQA_L2HDR Pablo Neira Ayuso
2026-11-16 0:16 ` [PATCH net-next 13/13] selftests: netfilter: add UDP flowtable offload test Pablo Neira Ayuso
2026-11-17 0:22 ` netdev-bot+sashiko
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=179491440753.514086.6452925778003138386.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=ja@ssi.bg \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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