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, horms@kernel.org
Subject: Re: [PATCH net 1/8] netfilter: nft_osf: restrict it to ipv4
Date: Thu, 23 Apr 2026 09:30:14 +0000 [thread overview]
Message-ID: <177693661488.73226.2217297170932768226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260420220215.111510-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Tue, 21 Apr 2026 00:02:08 +0200 you wrote:
> This expression only supports for ipv4, restrict it.
>
> Fixes: b96af92d6eaf ("netfilter: nf_tables: implement Passive OS fingerprint module in nft_osf")
> Acked-by: Florian Westphal <fw@strlen.de>
> Reviewed-by: Fernando Fernandez Mancera <fmancera@suse.de>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> [...]
Here is the summary with links:
- [net,1/8] netfilter: nft_osf: restrict it to ipv4
https://git.kernel.org/netdev/net/c/b336fdbb7103
- [net,2/8] netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO
https://git.kernel.org/netdev/net/c/2195574dc6d9
- [net,3/8] netfilter: conntrack: remove sprintf usage
https://git.kernel.org/netdev/net/c/6e7066bdb481
- [net,4/8] netfilter: xtables: restrict several matches to inet family
https://git.kernel.org/netdev/net/c/b6fe26f86a16
- [net,5/8] netfilter: nat: use kfree_rcu to release ops
https://git.kernel.org/netdev/net/c/6eda0d771f94
- [net,6/8] ipvs: fix MTU check for GSO packets in tunnel mode
https://git.kernel.org/netdev/net/c/67bf42cae41d
- [net,7/8] netfilter: nfnetlink_osf: fix out-of-bounds read on option matching
https://git.kernel.org/netdev/net/c/f5ca450087c3
- [net,8/8] netfilter: nfnetlink_osf: fix potential NULL dereference in ttl check
https://git.kernel.org/netdev/net/c/711987ba281f
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-04-23 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 22:02 [PATCH net 0/8] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 1/8] netfilter: nft_osf: restrict it to ipv4 Pablo Neira Ayuso
2026-04-23 9:30 ` patchwork-bot+netdevbpf [this message]
2026-04-20 22:02 ` [PATCH net 2/8] netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 3/8] netfilter: conntrack: remove sprintf usage Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 4/8] netfilter: xtables: restrict several matches to inet family Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 5/8] netfilter: nat: use kfree_rcu to release ops Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 6/8] ipvs: fix MTU check for GSO packets in tunnel mode Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 7/8] netfilter: nfnetlink_osf: fix out-of-bounds read on option matching Pablo Neira Ayuso
2026-04-20 22:02 ` [PATCH net 8/8] netfilter: nfnetlink_osf: fix potential NULL dereference in ttl check 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=177693661488.73226.2217297170932768226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--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