From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org
Subject: Re: [PATCH net 1/3] netfilter: nft_set_pipapo: fix null deref for empty set
Date: Wed, 13 Aug 2025 22:00:08 +0000 [thread overview]
Message-ID: <175512240826.3763733.8039499862730693344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250813113800.20775-2-fw@strlen.de>
Hello:
This series was applied to netdev/net.git (main)
by Florian Westphal <fw@strlen.de>:
On Wed, 13 Aug 2025 13:36:36 +0200 you wrote:
> Blamed commit broke the check for a null scratch map:
> - if (unlikely(!m || !*raw_cpu_ptr(m->scratch)))
> + if (unlikely(!raw_cpu_ptr(m->scratch)))
>
> This should have been "if (!*raw_ ...)".
> Use the pattern of the avx2 version which is more readable.
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: nft_set_pipapo: fix null deref for empty set
https://git.kernel.org/netdev/net/c/30c1d25b9870
- [net,2/3] ipvs: Fix estimator kthreads preferred affinity
https://git.kernel.org/netdev/net/c/c0a23bbc98e9
- [net,3/3] netfilter: nf_tables: reject duplicate device on updates
https://git.kernel.org/netdev/net/c/cf5fb87fcdaa
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:[~2025-08-13 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 11:36 [PATCH net 0/3] Netfilter fixes for net Florian Westphal
2025-08-13 11:36 ` [PATCH net 1/3] netfilter: nft_set_pipapo: fix null deref for empty set Florian Westphal
2025-08-13 22:00 ` patchwork-bot+netdevbpf [this message]
2025-08-13 11:36 ` [PATCH net 2/3] ipvs: Fix estimator kthreads preferred affinity Florian Westphal
2025-08-13 11:36 ` [PATCH net 3/3] netfilter: nf_tables: reject duplicate device on updates Florian Westphal
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=175512240826.3763733.8039499862730693344.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.