Netdev List
 help / color / mirror / Atom feed
From: "Zhou, Yun" <yun.zhou@windriver.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM
Date: Mon, 13 Jul 2026 17:42:58 +0800	[thread overview]
Message-ID: <8f58111e-f66e-476c-8a22-2017a02475a6@windriver.com> (raw)
In-Reply-To: <20260713085325.GA472073@shredder>



On 7/13/26 16:53, Ido Schimmel wrote:
> 
> Patch prefix should be [PATCH net]:
> 
> https://docs.kernel.org/process/maintainer-netdev.html
> 
> On Thu, Jul 09, 2026 at 06:52:43PM +0800, Yun Zhou wrote:
>> Before commit 00d066a4d4ed ("netdev_features: convert NETIF_F_LLTX to
>> dev->lltx"), NETIF_F_LLTX was set unconditionally in __gre_tunnel_init()
>> alongside GRE_FEATURES:
>>
>>      dev->features |= GRE_FEATURES | NETIF_F_LLTX;
>>
>> When that commit converted NETIF_F_LLTX to the dev->lltx flag, it
>> placed 'dev->lltx = true' after the SEQ/CSUM early returns instead
>> of before them. This causes GRE/GRETAP tunnels with SEQ or CSUM+encap
>> to lose lockless TX, reintroducing _xmit_lock acquisition around their
>> ndo_start_xmit. Since GRE xmit re-enters the stack via
>> ip_tunnel_xmit(), holding _xmit_lock risks ABBA deadlock with the
>> underlay device.
>>
>>    CPU0                        CPU1
>>    ----                        ----
>>    lock(&qdisc_xmit_lock_key#6);
>>                                lock(&qdisc_xmit_lock_key#3);
>>                                lock(&qdisc_xmit_lock_key#6);
>>    lock(&qdisc_xmit_lock_key#3);
>>
>> Fix by moving dev->lltx = true before the early returns, restoring
>> the original unconditional behavior.
>>
>> Fixes: 00d066a4d4ed ("netdev_features: convert NETIF_F_LLTX to dev->lltx")
> 
> Both sashiko instances indicate that this commit introduced the same bug
> in ip6gre_tnl_init_features(). Please perform the same fix there and
> fold it into v2.
> 

Thanks a lot for your review. IPv6 indeed has the same issue. I will fix 
it in v2 as you suggested.

BR,
Yun

      reply	other threads:[~2026-07-13  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 10:52 [PATCH] net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM Yun Zhou
2026-07-13  8:53 ` Ido Schimmel
2026-07-13  9:42   ` Zhou, Yun [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=8f58111e-f66e-476c-8a22-2017a02475a6@windriver.com \
    --to=yun.zhou@windriver.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.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