From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dave Young <hidave.darkstar@gmail.com>,
akpm@linux-foundation.org, bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [mmotm 2009-10-09-01-07] b43/wireless possible circular locking
Date: Sun, 11 Oct 2009 09:23:33 -0500 [thread overview]
Message-ID: <4AD1EA65.3070805@lwfinger.net> (raw)
In-Reply-To: <1255254687.4095.46.camel@johannes.local>
On 10/11/2009 04:51 AM, Johannes Berg wrote:
> On Sun, 2009-10-11 at 17:41 +0800, Dave Young wrote:
>> Hi,
>>
>> I got lockdep warnings about possible circular lock with
>> b43 interface startup. It looks like a real problem.
>>
>> [ 71.974542] wlan0: deauthenticating from 00:19:e0:db:24:de by local choice (reason=3)
>> [ 72.004352] b43-phy0 debug: Removing Interface type 2
>> [ 72.005431]
>> [ 72.005435] =======================================================
>> [ 72.006168] [ INFO: possible circular locking dependency detected ]
>> [ 72.006759] 2.6.32-rc3-mm1 #4
>> [ 72.007047] -------------------------------------------------------
>> [ 72.007617] ifconfig/2175 is trying to acquire lock:
>> [ 72.007617] (&(&rfkill->poll_work)->work){+.+...}, at: [<c0239375>] __cancel_work_timer+0x8c/0x18e
>> [ 72.007617]
>> [ 72.007617] but task is already holding lock:
>> [ 72.007617] (&wl->mutex){+.+.+.}, at: [<f8fa5359>] b43_op_stop+0x28/0x6a [b43]
>
> I believe this is already taken care of by Larry.
Yes, I introduced this bug and fixed it. The latest wireless-testing
should have the fix. In addition, it is on its way to Linus through
DameM. Unfortunately, that fix has another bug that will not show up
in the logs. With it, it is impossible to turn the radio back on after
it is killed via the rfkill switch. A "final" (And I hope that is
true!) fix is out for testing; however, the OP for the bug that
started this whole chain only has limited access to the machine in
question.
Larry
prev parent reply other threads:[~2009-10-11 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 9:41 [mmotm 2009-10-09-01-07] b43/wireless possible circular locking Dave Young
2009-10-11 9:51 ` Johannes Berg
2009-10-11 14:23 ` Larry Finger [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=4AD1EA65.3070805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=hidave.darkstar@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.