public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: security@kernel.org, edumazet@google.com, davem@davemloft.net,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	xmei5@asu.edu
Subject: Re: [PATCH net v4] net: add xmit recursion limit to tunnel xmit functions
Date: Tue, 10 Mar 2026 12:40:05 +0000	[thread overview]
Message-ID: <177314640530.2269130.10013467728563826261.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260306160133.3852900-2-bestswngs@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sat,  7 Mar 2026 00:01:34 +0800 you wrote:
> From: Weiming Shi <bestswngs@gmail.com>
> 
> Tunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own
> recursion limit. When a bond device in broadcast mode has GRE tap
> interfaces as slaves, and those GRE tunnels route back through the
> bond, multicast/broadcast traffic triggers infinite recursion between
> bond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing
> kernel stack overflow.
> 
> [...]

Here is the summary with links:
  - [net,v4] net: add xmit recursion limit to tunnel xmit functions
    https://git.kernel.org/netdev/net/c/6f1a9140ecda

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



      reply	other threads:[~2026-03-10 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:01 [PATCH net v4] net: add xmit recursion limit to tunnel xmit functions bestswngs
2026-03-10 12: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=177314640530.2269130.10013467728563826261.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=security@kernel.org \
    --cc=xmei5@asu.edu \
    /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