From: Paolo Abeni <pabeni@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>, Chris Arges <carges@cloudflare.com>
Cc: Weiming Shi <bestswngs@gmail.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, kernel-team@cloudflare.com,
jgriege@cloudflare.com
Subject: Re: [REGRESSION] net: add xmit recursion limit to tunnel xmit functions
Date: Thu, 2 Apr 2026 11:31:26 +0200 [thread overview]
Message-ID: <88deb91b-ef1b-403c-8eeb-0f971f27e34f@redhat.com> (raw)
In-Reply-To: <20260401173843.7a2bb607@kernel.org>
On 4/2/26 2:38 AM, Jakub Kicinski wrote:
> On Tue, 31 Mar 2026 15:09:33 -0500 Chris Arges wrote:
>> Commit 6f1a9140ecda ("net: add xmit recursion limit to tunnel xmit functions")
>> introduces a regression in our systems using legitimate multi-level tunnel
>> encapsulation stacks. Our testing was with stable 6.12.y and 6.18.y where this
>> patch was backported.
>>
>> One of the usecases we have are packets being sent to a GRE device, then
>> MPLS/LWT route, then IPIP device, then SIT/FOU device. What we observed is that
>> packets are getting dropped at the last device and we get the message "Dead
>> loop on virtual device" sent from the iptunnel_xmit function.
>
> Last device meaning limit of 5 would have worked for you?
> I don't think there was any hard math behind the 4 so ++
> on the limit may be simplest, but I defer to Paolo..
AFAICS the '4' limit was an empirical choice, and the reported splat
used 7 devices, so moving to 5 should fit, even if I must admit it feels
a bit a whack a mole situation. On the flip side a revert of the blamed
commit feels not safe.
@Chris, could you please share a patch increasing the limit to 5?
Thanks,
Paolo
prev parent reply other threads:[~2026-04-02 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:09 [REGRESSION] net: add xmit recursion limit to tunnel xmit functions Chris Arges
2026-04-02 0:38 ` Jakub Kicinski
2026-04-02 9:31 ` Paolo Abeni [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=88deb91b-ef1b-403c-8eeb-0f971f27e34f@redhat.com \
--to=pabeni@redhat.com \
--cc=bestswngs@gmail.com \
--cc=carges@cloudflare.com \
--cc=edumazet@google.com \
--cc=jgriege@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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