From: Luciano Coelho <coelho@ti.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [3.0-rc4] lockdep: netdev notifier vs rfkill
Date: Thu, 30 Jun 2011 08:34:17 +0300 [thread overview]
Message-ID: <1309412057.1514.123.camel@cumari> (raw)
In-Reply-To: <BANLkTimPMypvBWp-xv4WH_mD+WAOQQgRdA@mail.gmail.com>
On Tue, 2011-06-21 at 21:10 +0800, Daniel J Blueman wrote:
> When hitting the hard rfkill in 3.0-rc4, lockdep spots some likely lock misuse:
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 3.0.0-rc4-340c #1
> -------------------------------------------------------
> kworker/0:0/4 is trying to acquire lock:
> (&rdev->mtx){+.+.+.}, at: [<ffffffff816cefce>]
> cfg80211_netdev_notifier_call+0x11e/0x650
>
> but task is already holding lock:
> (&rdev->devlist_mtx){+.+.+.}, at: [<ffffffff816cff16>]
> cfg80211_rfkill_set_block+0x46/0xa0
>
> which lock already depends on the new lock.
This should be fixed with the patch for 3.0 that I have just sent,
"cfg80211: fix deadlock with rfkill/sched_scan by adding new mutex".
--
Cheers,
Luca.
prev parent reply other threads:[~2011-06-30 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 13:10 [3.0-rc4] lockdep: netdev notifier vs rfkill Daniel J Blueman
2011-06-30 5:34 ` Luciano Coelho [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=1309412057.1514.123.camel@cumari \
--to=coelho@ti.com \
--cc=daniel.blueman@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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