From: "Zhou, Yun" <yun.zhou@windriver.com>
To: Paolo Abeni <pabeni@redhat.com>,
dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: erspan: set lltx to avoid sch_direct_xmit deadlock
Date: Thu, 9 Jul 2026 17:18:21 +0800 [thread overview]
Message-ID: <c58de90a-0ba8-45aa-a9ce-37d996ac0173@windriver.com> (raw)
In-Reply-To: <695fc2fb-606e-4d5a-a4d6-41ba5d1cfadb@redhat.com>
On 7/9/26 16:16, Paolo Abeni wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On 7/9/26 8:56 AM, Yun Zhou wrote:
>> erspan_xmit() re-enters the network stack via ip_tunnel_xmit(), causing
>> nested acquisition of _xmit_lock on the underlay device while already
>> holding the ERSPAN device's _xmit_lock. Both are ARPHRD_ETHER and share
>> the same lockdep class, creating an ABBA deadlock:
>>
>> sch_direct_xmit [lock erspan] -> erspan_xmit -> ip_tunnel_xmit ->
>> ip_output -> __dev_queue_xmit -> sch_direct_xmit [lock underlay]
>>
>> Set dev->lltx = true so HARD_TX_LOCK() skips the spinlock for ERSPAN.
>> This is safe as erspan_xmit() has no shared mutable state: o_seqno is
>> atomic, stats use atomic_long_inc, and dst_cache is per-CPU. GRETAP,
>> the sibling device with identical xmit structure, already sets lltx.
>>
>> Closes: https://syzkaller.appspot.com/bug?extid=9bda1b9fbb7fbdf9b62b
>> Reported-by: syzbot+9bda1b9fbb7fbdf9b62b@syzkaller.appspotmail.com
>> Fixes: 84e54fe0a5ea ("gre: introduce native tunnel support for ERSPAN")
>> Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
> So this is actually a v2 of:
>
> 20260630183702.170798-2-hemendranaik@gmail.com/20260630183702.170798-2-hemendranaik@gmail.com/
>
> right?
>
> please have a look at:
>
> https://elixir.bootlin.com/linux/v7.1/source/Documentation/process/maintainer-netdev.rst#L434
>
> any kind of re-submission matters, no matter how trivial is the reason.
>
> /P
>
I sincerely apologize for the duplicate patch submission. It was a minor
oversight caused by a misconfigured Git in my new environment. However,
it seems this email was sent to hemendranaik@gmail.com, right?
BR,
Yun
next prev parent reply other threads:[~2026-07-09 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:56 [PATCH] net: erspan: set lltx to avoid sch_direct_xmit deadlock Yun Zhou
2026-07-09 8:16 ` Paolo Abeni
2026-07-09 9:18 ` Zhou, Yun [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-09 6:54 Yun Zhou
2026-07-09 6:57 ` Zhou, Yun
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=c58de90a-0ba8-45aa-a9ce-37d996ac0173@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