Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, idosch@nvidia.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net 0/5] vxlan: fixes for skb header pulling, cloning, and concurrency in TX path
Date: Mon, 27 Jul 2026 22:20:14 +0000	[thread overview]
Message-ID: <178519081439.1438149.9964994403832943446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260723144249.759100-1-edumazet@google.com>

Hello:

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

On Thu, 23 Jul 2026 14:42:44 +0000 you wrote:
> While working on RTNL-less fill_info for vxlan, Sashiko found annoying
> pre-existing issues, adding noise to an already complex work.
> 
> This series addresses some of them in VXLAN transmit path,
> primarily within route_shortcircuit(), header validation, and neighbour lookup.
> 
> Patch 1 fixes a potential use-after-free in vxlan_xmit() caused by caching
> the Ethernet header pointer ('eth') before calling route_shortcircuit(), which
> can reallocate skb->head via pskb_may_pull().
> 
> [...]

Here is the summary with links:
  - [net,1/5] vxlan: re-fetch eth header after route_shortcircuit()
    https://git.kernel.org/netdev/net/c/1395a676ec15
  - [net,2/5] vxlan: unclone skb head before modifying eth header in route_shortcircuit()
    https://git.kernel.org/netdev/net/c/760d36e737f2
  - [net,3/5] vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    https://git.kernel.org/netdev/net/c/8eca411347e1
  - [net,4/5] vxlan: use pskb_network_may_pull() in route_shortcircuit()
    https://git.kernel.org/netdev/net/c/26bb2dd0a883
  - [net,5/5] vxlan: use pskb_network_may_pull() for transmit path header pulls
    https://git.kernel.org/netdev/net/c/b9553558b48d

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-07-27 22:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 14:42 [PATCH net 0/5] vxlan: fixes for skb header pulling, cloning, and concurrency in TX path Eric Dumazet
2026-07-23 14:42 ` [PATCH net 1/5] vxlan: re-fetch eth header after route_shortcircuit() Eric Dumazet
2026-07-23 16:37   ` Vadim Fedorenko
2026-07-23 14:42 ` [PATCH net 2/5] vxlan: unclone skb head before modifying eth header in route_shortcircuit() Eric Dumazet
2026-07-23 14:42 ` [PATCH net 3/5] vxlan: use neigh_ha_snapshot() " Eric Dumazet
2026-07-23 16:41   ` Vadim Fedorenko
2026-07-23 14:42 ` [PATCH net 4/5] vxlan: use pskb_network_may_pull() " Eric Dumazet
2026-07-23 16:42   ` Vadim Fedorenko
2026-07-23 14:42 ` [PATCH net 5/5] vxlan: use pskb_network_may_pull() for transmit path header pulls Eric Dumazet
2026-07-23 16:43   ` Vadim Fedorenko
2026-07-26 10:34   ` Ido Schimmel
2026-07-27 22:20 ` 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=178519081439.1438149.9964994403832943446.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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