From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, razor@blackwall.org,
ja@ssi.bg, petrm@nvidia.com, fw@strlen.de, kuniyu@google.com,
bridge@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] bridge: Validate and clean up IPv6 neighbour suppression
Date: Fri, 07 Aug 2026 23:40:21 +0000 [thread overview]
Message-ID: <178614602190.2465504.10010813956529839994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260803112505.613873-1-danieller@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 3 Aug 2026 14:25:00 +0300 you wrote:
> The bridge implements IPv6 neighbour suppression by snooping Neighbour
> Solicitation and Neighbour Advertisement messages, but it previously only
> checked the ICMPv6 type and code before acting on them. This leaves it
> open to acting on malformed or spoofed packets that any RFC 4861 compliant
> node should reject, and the option parsing in br_nd_send() open-codes a
> loop that has historically been a source of bugs.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] bridge: Use direct pointer in br_is_nd_neigh_msg()
https://git.kernel.org/netdev/net-next/c/2cad8e3d9d94
- [net-next,v2,2/5] ipv6: ndisc: Add ndisc_check_ns_na() validation helper
https://git.kernel.org/netdev/net-next/c/9dfa6cca8959
- [net-next,v2,3/5] bridge: Validate NS/NA messages using ndisc_check_ns_na()
https://git.kernel.org/netdev/net-next/c/18668f4747c9
- [net-next,v2,4/5] bridge: Linearize skb once the ND message type is validated
https://git.kernel.org/netdev/net-next/c/67b14d6e36cf
- [net-next,v2,5/5] bridge: Use ndisc_parse_options() to parse ND options in br_nd_send()
https://git.kernel.org/netdev/net-next/c/7445aaa9fe6d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-07 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 11:25 [PATCH net-next v2 0/5] bridge: Validate and clean up IPv6 neighbour suppression Danielle Ratson
2026-08-03 11:25 ` [PATCH net-next v2 1/5] bridge: Use direct pointer in br_is_nd_neigh_msg() Danielle Ratson
2026-08-05 8:06 ` Danielle Ratson
2026-08-03 11:25 ` [PATCH net-next v2 2/5] ipv6: ndisc: Add ndisc_check_ns_na() validation helper Danielle Ratson
2026-08-05 8:06 ` Danielle Ratson
2026-08-03 11:25 ` [PATCH net-next v2 3/5] bridge: Validate NS/NA messages using ndisc_check_ns_na() Danielle Ratson
2026-08-03 11:25 ` [PATCH net-next v2 4/5] bridge: Linearize skb once the ND message type is validated Danielle Ratson
2026-08-03 15:25 ` Nikolay Aleksandrov
2026-08-03 11:25 ` [PATCH net-next v2 5/5] bridge: Use ndisc_parse_options() to parse ND options in br_nd_send() Danielle Ratson
2026-08-05 8:07 ` Danielle Ratson
2026-08-07 23:40 ` patchwork-bot+netdevbpf [this message]
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=178614602190.2465504.10010813956529839994.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=ja@ssi.bg \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.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