All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	willemb@google.com, horms@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] nsh: limit recursion in nsh_gso_segment()
Date: Thu, 12 Nov 2026 19:40:05 +0000	[thread overview]
Message-ID: <179451240578.614223.5418531856983381502.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112102001.3744643-1-edumazet@kernel.org>

Hello:

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

On Thu, 12 Nov 2026 11:19:59 +0100 you wrote:
> Sashiko found that nsh_gso_segment() can call itself, through
> skb_mac_gso_segment(), once per stacked NSH header. Nothing limits the
> depth, and a 64KB GSO packet made of 8-byte NSH headers overflows the
> kernel stack. It was reported while reviewing an unrelated virtio
> series [1].
> 
> Such a packet can be sent with a packet socket using PACKET_VNET_HDR,
> when the nsh module is loaded.
> 
> [...]

Here is the summary with links:
  - [net,1/2] nsh: limit recursion in nsh_gso_segment()
    https://git.kernel.org/netdev/net/c/3921fb102d78
  - [net,2/2] selftests: net: add a test for NSH GSO
    https://git.kernel.org/netdev/net/c/53e7352d65f7

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-11-12 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 10:19 [PATCH net 0/2] nsh: limit recursion in nsh_gso_segment() Eric Dumazet
2026-11-12 10:20 ` [PATCH net 1/2] " Eric Dumazet
2026-11-12 10:33   ` Jiri Benc
2026-11-12 22:54   ` David Laight
2026-11-12 10:20 ` [PATCH net 2/2] selftests: net: add a test for NSH GSO Eric Dumazet
2026-11-12 19: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=179451240578.614223.5418531856983381502.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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 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.