public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chris J Arges <carges@cloudflare.com>
Cc: pabeni@redhat.com, bestswngs@gmail.com,
	kernel-team@cloudflare.com, davem@davemloft.net,
	dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
	horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: increase IP_TUNNEL_RECURSION_LIMIT to 5
Date: Fri, 03 Apr 2026 23:10:11 +0000	[thread overview]
Message-ID: <177525781153.1484550.12909055678943447025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260402222401.3408368-1-carges@cloudflare.com>

Hello:

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

On Thu,  2 Apr 2026 17:23:16 -0500 you wrote:
> In configurations with multiple tunnel layers and MPLS lwtunnel routing, a
> single tunnel hop can increment the counter beyond this limit. This causes
> packets to be dropped with the "Dead loop on virtual device" message even
> when a routing loop doesn't exist.
> 
> Increase IP_TUNNEL_RECURSION_LIMIT from 4 to 5 to handle this use-case.
> 
> [...]

Here is the summary with links:
  - net: increase IP_TUNNEL_RECURSION_LIMIT to 5
    https://git.kernel.org/netdev/net/c/77facb35227c

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



      reply	other threads:[~2026-04-03 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 22:23 [PATCH] net: increase IP_TUNNEL_RECURSION_LIMIT to 5 Chris J Arges
2026-04-03 23: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=177525781153.1484550.12909055678943447025.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=carges@cloudflare.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.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