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@google.com
Subject: Re: [PATCH net 1/7] netfilter: nf_tables: always release netdev hooks from notifier
Date: Thu, 11 May 2023 02:20:22 +0000 [thread overview]
Message-ID: <168377162238.11094.15038235357887196732.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230510083313.152961-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 10 May 2023 10:33:07 +0200 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> This reverts "netfilter: nf_tables: skip netdev events generated on netns removal".
>
> The problem is that when a veth device is released, the veth release
> callback will also queue the peer netns device for removal.
>
> [...]
Here is the summary with links:
- [net,1/7] netfilter: nf_tables: always release netdev hooks from notifier
https://git.kernel.org/netdev/net/c/dc1c9fd4a8bb
- [net,2/7] netfilter: conntrack: fix possible bug_on with enable_hooks=1
https://git.kernel.org/netdev/net/c/e72eeab542db
- [net,3/7] selftests: nft_flowtable.sh: use /proc for pid checking
https://git.kernel.org/netdev/net/c/0a11073e8e33
- [net,4/7] selftests: nft_flowtable.sh: no need for ps -x option
https://git.kernel.org/netdev/net/c/0749d670d758
- [net,5/7] selftests: nft_flowtable.sh: wait for specific nc pids
https://git.kernel.org/netdev/net/c/1114803c2da9
- [net,6/7] selftests: nft_flowtable.sh: monitor result file sizes
https://git.kernel.org/netdev/net/c/90ab51226d52
- [net,7/7] selftests: nft_flowtable.sh: check ingress/egress chain too
https://git.kernel.org/netdev/net/c/3acf8f6c14d0
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:[~2023-05-11 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 8:33 [PATCH net 0/7] Netfilter updates for net Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 1/7] netfilter: nf_tables: always release netdev hooks from notifier Pablo Neira Ayuso
2023-05-11 2:20 ` patchwork-bot+netdevbpf [this message]
2023-05-10 8:33 ` [PATCH net 2/7] netfilter: conntrack: fix possible bug_on with enable_hooks=1 Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 3/7] selftests: nft_flowtable.sh: use /proc for pid checking Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 4/7] selftests: nft_flowtable.sh: no need for ps -x option Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 5/7] selftests: nft_flowtable.sh: wait for specific nc pids Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 6/7] selftests: nft_flowtable.sh: monitor result file sizes Pablo Neira Ayuso
2023-05-10 8:33 ` [PATCH net 7/7] selftests: nft_flowtable.sh: check ingress/egress chain too Pablo Neira Ayuso
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=168377162238.11094.15038235357887196732.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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