From: patchwork-bot+netdevbpf@kernel.org
To: zihan xi <zihanx@nebusec.ai>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
idosch@nvidia.com, kuniyu@google.com, willemb@google.com,
kees@kernel.org, richardbgobert@gmail.com
Subject: Re: [PATCH net v6 0/1] net: gso: limit recursive IP-in-IP segmentation
Date: Tue, 29 Sep 2026 10:10:11 +0000 [thread overview]
Message-ID: <179067661177.399852.14443829829984221646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924051521.32568-1-zihanx@nebusec.ai>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 24 Sep 2026 05:15:20 +0000 you wrote:
> Hi Linux kernel maintainers,
>
> This reroll uses IP_TUNNEL_RECURSION_LIMIT directly for the shared
> IPv4/IPv6 GSO recursion check and adds the requested Closes tag.
>
> The v5 cover letter has the bug details, PoC, and validation evidence:
> https://lore.kernel.org/all/cover.1790157745.git.zihanx@nebusec.ai/
>
> [...]
Here is the summary with links:
- [net,v6,1/1] net: gso: limit recursive IP-in-IP segmentation
https://git.kernel.org/netdev/net/c/006c8b834aed
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-09-29 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:15 [PATCH net v6 0/1] net: gso: limit recursive IP-in-IP segmentation Zihan Xi
2026-09-24 5:15 ` [PATCH net v6 1/1] " Zihan Xi
2026-09-25 21:13 ` Willem de Bruijn
2026-09-29 10:10 ` 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=179067661177.399852.14443829829984221646.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=willemb@google.com \
--cc=zihanx@nebusec.ai \
/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.