Hello:
This series was applied to netdev/net.git (main)
by Florian Westphal <fw@xxxxxxxxx>:
On Thu, 20 Jul 2023 18:51:33 +0200 you wrote:
> On some platforms there is a padding hole in the nft_verdict
> structure, between the verdict code and the chain pointer.
>
> On element insertion, if the new element clashes with an existing one and
> NLM_F_EXCL flag isn't set, we want to ignore the -EEXIST error as long as
> the data associated with duplicated element is the same as the existing
> one. The data equality check uses memcmp.
>
> [...]
Here is the summary with links:
- [net,1/5] netfilter: nf_tables: fix spurious set element insertion failure
https://git.kernel.org/netdev/net/c/ddbd8be68941
- [net,2/5] netfilter: nf_tables: can't schedule in nft_chain_validate
https://git.kernel.org/netdev/net/c/314c82841602
- [net,3/5] netfilter: nft_set_pipapo: fix improper element removal
https://git.kernel.org/netdev/net/c/87b5a5c20940
- [net,4/5] netfilter: nf_tables: skip bound chain in netns release path
https://git.kernel.org/netdev/net/c/751d460ccff3
- [net,5/5] netfilter: nf_tables: skip bound chain on rule flush
https://git.kernel.org/netdev/net/c/6eaf41e87a22
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
