From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Ray Lee <ray-lk@madrabbit.org>, Dan Williams <dcbw@redhat.com>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
Date: Tue, 21 Nov 2006 19:32:42 +0100 [thread overview]
Message-ID: <1164133962.3631.14.camel@johannes.berg> (raw)
In-Reply-To: <45633FF8.6010209@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Tue, 2006-11-21 at 12:05 -0600, Larry Finger wrote:
> Although my understanding of locking has been shown to be deficient, it looks to me as if the
> deadlock involves a WX call while a scan is in progress. The following patch uses
> mutex_trylock rather than mutex_lock so that WX calls are rejected if the lock is already held.
> Please try this patch with wpa_supplicant and NetworkManager both running. I have tested it with
> wpa_supplicant alone.
I don't think this is the right thing to do. This cannot be causing the
deadlock as for a deadlock you need (at least) two locks. Now, since any
calls from userspace to d80211 acquire the mutex first, they should be
fine. They also both acquire the rtnl lock first.
The deadlock must be somewhere deeper. Can we run this with lockdep
enabled? Might give us a hint before we dig out all the used locks
here...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-21 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4561DBE0.2060908@lwfinger.net>
2006-11-21 5:17 ` Ray Lee
2006-11-21 18:05 ` Larry Finger
2006-11-21 18:32 ` Johannes Berg [this message]
2006-11-21 18:36 ` Johannes Berg
2006-11-21 18:49 ` Larry Finger
2006-11-22 13:58 ` Dan Williams
2006-11-22 17:11 ` Ray Lee
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=1164133962.3631.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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
all inboxes | Powered by JetHome®