Netdev List
 help / color / mirror / Atom feed
From: Andrew Gaylard <ag@ffroot.co.za>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,  wellslutw@gmail.com,
	 andrew+netdev@lunn.ch, davem@davemloft.net,
	 edumazet@google.com,  pabeni@redhat.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] net: sunplus: fix tx_poll spin_lock missing irqsave in NAPI context
Date: Mon, 24 Aug 2026 14:33:36 +0200	[thread overview]
Message-ID: <sa67blfpujj.fsf@dev-ag> (raw)
In-Reply-To: <20260822135103.6711ba25@kernel.org> (Jakub Kicinski's message of "Sat, 22 Aug 2026 13:51:03 -0700")

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 20 Aug 2026 15:01:59 +0200 Andrew Gaylard wrote:
>> spl2sw_tx_poll() runs in NAPI (softirq) context and acquires
>> comm->tx_lock with plain spin_lock(). The hardirq handler
>> spl2sw_ethernet_interrupt() acquires the same lock, so a hardirq on
>> the same CPU while the NAPI poll holds the lock would deadlock with
>> IRQs disabled. Use spin_lock_irqsave/spin_unlock_irqrestore.
>
> Please explain how the issue was found and how the fix was tested.
> I mean - this is an ancient driver, if you don't have a way to test the
> fix you should not be sending the patch.

I'm testing on a Tibbo LTTP3G2 board:
https://tibbo.com/store/tps/ltpp3g2.html

This work is part of getting it to boot, getting it stable, adding a
couple of missing drivers, and sending the changes upstream.

I found the issue using lockdep. At least, I though I did, but I've not
been able to reproduce it, so I must have been mistaken.

Apologies.  Please drop this patch.

-- 
Andrew

      reply	other threads:[~2026-08-24 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 13:01 [PATCH] net: sunplus: fix tx_poll spin_lock missing irqsave in NAPI context Andrew Gaylard
2026-08-22 20:50 ` Jakub Kicinski
2026-08-22 20:51 ` Jakub Kicinski
2026-08-24 12:33   ` Andrew Gaylard [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=sa67blfpujj.fsf@dev-ag \
    --to=ag@ffroot.co.za \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wellslutw@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