From: Jakub Kicinski <kuba@kernel.org>
To: Tristan Madani <tristmd@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
maheshb@google.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: Re: [PATCH net v2] net: reduce XMIT_RECURSION_LIMIT under KASAN
Date: Tue, 21 Jul 2026 13:04:41 -0700 [thread overview]
Message-ID: <20260721130441.3c662a9a@kernel.org> (raw)
In-Reply-To: <20260711204700.1760374-1-tristmd@gmail.com>
On Sat, 11 Jul 2026 20:47:00 +0000 Tristan Madani wrote:
> Virtual network devices (ipvlan, macvlan, bonding) can enter legitimate
> transmit recursion when combined with packet forwarding configurations
> such as IPVS NAT. The existing XMIT_RECURSION_LIMIT (8) in
> __dev_queue_xmit() detects and breaks these loops, but the allowed
> depth is too high for KASAN-instrumented kernels: each recursion level
> consumes significantly more stack due to KASAN inline instrumentation,
> and the cumulative usage overflows the kernel stack before the limit
> fires.
This patch was marked as changes requested, I'm not sure why.
If it is still valid please repost (please start a new thread,
please add a link to the previous posting under --- like this:
v3:
- no changes
v2: https://lore.kernel.org/20260711204700.1760374-1-tristmd@gmail.com
prev parent reply other threads:[~2026-07-21 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 13:47 [PATCH net] ipvlan: add xmit recursion protection Tristan Madani
2026-07-11 14:00 ` Eric Dumazet
2026-07-11 20:47 ` [PATCH net v2] net: reduce XMIT_RECURSION_LIMIT under KASAN Tristan Madani
2026-07-21 20:04 ` Jakub Kicinski [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=20260721130441.3c662a9a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.com \
--cc=tristmd@gmail.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
all inboxes | Powered by JetHome®