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, fw@strlen.de
Subject: Re: [PATCH net 1/3] netfilter: xtables: avoid NFPROTO_UNSPEC where needed
Date: Thu, 10 Oct 2024 12:00:30 +0000 [thread overview]
Message-ID: <172856163076.1995536.7466933968388077286.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241009213858.3565808-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 9 Oct 2024 23:38:56 +0200 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> syzbot managed to call xt_cluster match via ebtables:
>
> WARNING: CPU: 0 PID: 11 at net/netfilter/xt_cluster.c:72 xt_cluster_mt+0x196/0x780
> [..]
> ebt_do_table+0x174b/0x2a40
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: xtables: avoid NFPROTO_UNSPEC where needed
https://git.kernel.org/netdev/net/c/0bfcb7b71e73
- [net,2/3] netfilter: fib: check correct rtable in vrf setups
https://git.kernel.org/netdev/net/c/05ef7055debc
- [net,3/3] selftests: netfilter: conntrack_vrf.sh: add fib test case
https://git.kernel.org/netdev/net/c/c6a0862bee69
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:[~2024-10-10 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 21:38 [PATCH net 0/3] Netfilter fixes for net Pablo Neira Ayuso
2024-10-09 21:38 ` [PATCH net 1/3] netfilter: xtables: avoid NFPROTO_UNSPEC where needed Pablo Neira Ayuso
2024-10-10 12:00 ` patchwork-bot+netdevbpf [this message]
2024-10-09 21:38 ` [PATCH net 2/3] netfilter: fib: check correct rtable in vrf setups Pablo Neira Ayuso
2024-10-09 21:38 ` [PATCH net 3/3] selftests: netfilter: conntrack_vrf.sh: add fib test case 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=172856163076.1995536.7466933968388077286.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--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;
as well as URLs for NNTP newsgroup(s).