From: Johannes Berg <[email protected]>
To: Ammar Faizi <[email protected]>,
Linux Kernel Mailing List <[email protected]>
Cc: "David S. Miller" <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Jakub Kicinski <[email protected]>, Kalle Valo <[email protected]>,
Linux Wireless Mailing List <[email protected]>,
netdev Mailing List <[email protected]>,
Paolo Abeni <[email protected]>,
Yan-Hsuan Chuang <[email protected]>
Subject: Re: [Linux 5.18-rc1] WARNING: possible circular locking dependency detected at (rtw_ops_config, ieee80211_mgd_probe_ap)
Date: Mon, 11 Apr 2022 16:46:47 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 2022-04-07 at 08:26 +0700, Ammar Faizi wrote:
>
> [21860.955836] Possible unsafe locking scenario:
>
> [21860.955837] CPU0 CPU1
> [21860.955837] ---- ----
> [21860.955838] lock(&local->iflist_mtx);
> [21860.955839] lock(&rtwdev->mutex);
> [21860.955840] lock(&local->iflist_mtx);
> [21860.955841] lock(&rtwdev->mutex);
> [21860.955842]
> *** DEADLOCK ***
>
The driver needs to fix this, cannot call ieee80211_iterate_interfaces()
inside a section locked this way. I _think_ this deadlock used to be
documented by it looks like that documentation got moved around or
something.
johannes
prev parent reply other threads:[~2022-04-11 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 6:47 [Linux 5.18-rc1] WARNING: possible circular locking dependency detected at (rtw_ops_config, ieee80211_mgd_probe_ap) Ammar Faizi
2022-04-07 1:26 ` Ammar Faizi
2022-04-11 14:46 ` Johannes Berg [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=446ea9872d46fe0ad594cfa6d3df224cfcb5223f.camel@sipsolutions.net \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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