public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yang <n05ec@lzu.edu.cn>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, razor@blackwall.org, idosch@nvidia.com,
	andrew+netdev@lunn.ch, horms@kernel.org,
	florian.fainelli@broadcom.com, roopa@cumulusnetworks.com,
	dlstevens@us.ibm.com, nb@tipi-net.de, netdev@vger.kernel.org,
	bridge@lists.linux.dev, linux-kernel@vger.kernel.org,
	yifanwucs@gmail.com, tomapufckgml@gmail.com,
	tanyuan98@outlook.com, bird@lzu.edu.cn
Subject: Re: [PATCH net 0/3] bridge/vxlan: harden ND option parsing paths
Date: Sat, 28 Mar 2026 03:40:13 +0000	[thread overview]
Message-ID: <177466921304.4169512.6574568898601672683.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260326034441.2037420-1-n05ec@lzu.edu.cn>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 26 Mar 2026 03:44:38 +0000 you wrote:
> Hi,
> 
> This series hardens ND option parsing in bridge and vxlan paths.
> 
> Patch 1 linearizes the request skb in br_nd_send() before walking ND
> options. Patch 2 adds explicit ND option length validation in
> br_nd_send(). Patch 3 adds matching ND option length validation in
> vxlan_na_create().
> 
> [...]

Here is the summary with links:
  - [net,1/3] bridge: br_nd_send: linearize skb before parsing ND options
    https://git.kernel.org/netdev/net/c/a01aee7cafc5
  - [net,2/3] bridge: br_nd_send: validate ND option lengths
    https://git.kernel.org/netdev/net/c/850837965af1
  - [net,3/3] vxlan: validate ND option lengths in vxlan_na_create
    https://git.kernel.org/netdev/net/c/afa9a05e6c49

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-03-28  3:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  3:44 [PATCH net 0/3] bridge/vxlan: harden ND option parsing paths Yang Yang
2026-03-26  3:44 ` [PATCH net 1/3] bridge: br_nd_send: linearize skb before parsing ND options Yang Yang
2026-03-26 16:29   ` Ido Schimmel
2026-03-27  6:37   ` Nikolay Aleksandrov
2026-03-26  3:44 ` [PATCH net 2/3] bridge: br_nd_send: validate ND option lengths Yang Yang
2026-03-26 16:30   ` Ido Schimmel
2026-03-27  6:37   ` Nikolay Aleksandrov
2026-03-26  3:44 ` [PATCH net 3/3] vxlan: validate ND option lengths in vxlan_na_create Yang Yang
2026-03-26 16:30   ` Ido Schimmel
2026-03-27  6:38   ` Nikolay Aleksandrov
2026-03-28  3: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=177466921304.4169512.6574568898601672683.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bird@lzu.edu.cn \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=dlstevens@us.ibm.com \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n05ec@lzu.edu.cn \
    --cc=nb@tipi-net.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=tanyuan98@outlook.com \
    --cc=tomapufckgml@gmail.com \
    --cc=yifanwucs@gmail.com \
    /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