From: Jakub Kicinski <kuba@kernel.org>
To: Pavel Begunkov <asml.silence@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: Breno Leitao <leitao@debian.org>, Mike Galbraith <efault@gmx.de>,
paulmck@kernel.org, LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, boqun.feng@gmail.com
Subject: Re: netconsole: HARDIRQ-safe -> HARDIRQ-unsafe lock order warning
Date: Fri, 15 Aug 2025 09:42:17 -0700 [thread overview]
Message-ID: <20250815094217.1cce7116@kernel.org> (raw)
In-Reply-To: <3d20ce1b-7a9b-4545-a4a9-23822b675e0c@gmail.com>
On Fri, 15 Aug 2025 11:44:45 +0100 Pavel Begunkov wrote:
> On 8/15/25 01:23, Jakub Kicinski wrote:
> > On Thu, 14 Aug 2025 03:16:11 -0700 Breno Leitao wrote:
> >> 2.2) netpoll // net poll will call the network subsystem to send the packet
> >> 2.3) lock(&fq->lock); // Try to get the lock while the lock was already held
>
> The report for reference:
>
> https://lore.kernel.org/all/fb38cfe5153fd67f540e6e8aff814c60b7129480.camel@gmx.de/>
> > Where does netpoll take fq->lock ?
>
> the dependencies between the lock to be acquired
> [ 107.985514] and HARDIRQ-irq-unsafe lock:
> [ 107.985531] -> (&fq->lock){+.-.}-{3:3} {
> ...
> [ 107.988053] ... acquired at:
> [ 107.988054] check_prev_add+0xfb/0xca0
> [ 107.988058] validate_chain+0x48c/0x530
> [ 107.988061] __lock_acquire+0x550/0xbc0
> [ 107.988064] lock_acquire.part.0+0xa1/0x210
> [ 107.988068] _raw_spin_lock_bh+0x38/0x50
> [ 107.988070] ieee80211_queue_skb+0xfd/0x350 [mac80211]
> [ 107.988198] __ieee80211_xmit_fast+0x202/0x360 [mac80211]
> [ 107.988314] ieee80211_xmit_fast+0xfb/0x1f0 [mac80211]
> [ 107.988424] __ieee80211_subif_start_xmit+0x14e/0x3d0 [mac80211]
> [ 107.988530] ieee80211_subif_start_xmit+0x46/0x230 [mac80211]
Ah, that's WiFi's stack queuing. Dunno whether we expect netpoll to
work over WiFi. I suspect disabling netconsole over WiFi may be the
most sensible way out. Johannes, do you expect mac80211 Tx to be IRQ-safe?
next prev parent reply other threads:[~2025-08-15 16:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb38cfe5153fd67f540e6e8aff814c60b7129480.camel@gmx.de>
2025-08-14 10:16 ` netconsole: HARDIRQ-safe -> HARDIRQ-unsafe lock order warning Breno Leitao
2025-08-14 15:45 ` Pavel Begunkov
2025-08-15 0:23 ` Jakub Kicinski
2025-08-15 10:44 ` Pavel Begunkov
2025-08-15 16:42 ` Jakub Kicinski [this message]
2025-08-15 17:29 ` Breno Leitao
2025-08-15 17:33 ` Jakub Kicinski
2025-08-18 12:23 ` Breno Leitao
2025-08-15 19:10 ` Calvin Owens
2025-08-16 9:19 ` Mike Galbraith
2025-08-15 20:02 ` Pavel Begunkov
2025-08-18 12:10 ` Breno Leitao
2025-08-19 17:27 ` Breno Leitao
2025-08-20 12:31 ` Mike Galbraith
2025-08-20 17:36 ` Breno Leitao
2025-08-21 3:37 ` Mike Galbraith
2025-08-21 3:51 ` Mike Galbraith
2025-08-21 17:35 ` Breno Leitao
2025-08-22 3:54 ` Mike Galbraith
2025-08-26 12:43 ` Breno Leitao
2025-08-26 13:56 ` Mike Galbraith
2025-09-05 12:48 ` John Ogness
2025-08-21 10:06 ` Mike Galbraith
2025-08-21 13:12 ` Mike Galbraith
2025-08-15 17:37 ` Calvin Owens
2025-08-26 14:10 ` Johannes Berg
2025-08-15 12:45 ` Mike Galbraith
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=20250815094217.1cce7116@kernel.org \
--to=kuba@kernel.org \
--cc=asml.silence@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=efault@gmx.de \
--cc=johannes@sipsolutions.net \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).