From: Dan Williams <dcbw@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Ray Lee <ray-lk@madrabbit.org>,
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: Wed, 22 Nov 2006 08:58:10 -0500 [thread overview]
Message-ID: <1164203890.3474.1.camel@localhost.localdomain> (raw)
In-Reply-To: <45634A4A.1040909@lwfinger.net>
On Tue, 2006-11-21 at 12:49 -0600, Larry Finger wrote:
> Johannes Berg wrote:
> > On Tue, 2006-11-21 at 19:32 +0100, Johannes Berg wrote:
> >
> >> I don't think this is the right thing to do.
> >
> > Or put differently, this won't fix the problem if that "something:
> > that's triggering the deadlock happens while you're in the locked
> > section.
>
> I'm going to install NM on my system to see if I can trigger the problem with lockdep enabled.
If you don't want to go that far, just run a bunch of "iwlist eth1 scan"
and "iwconfig eth1" over and over and you'll effectively simulate the
behavior of NM in this situation (although doing it a lot quicker than
NM likely).
Setting up a script to just run those two in parallel continuously is
probably a good test of any WE locking in a driver :)
Dan
> Larry
next prev parent reply other threads:[~2006-11-22 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4561DBE0.2060908@lwfinger.net>
2006-11-21 5:17 ` RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock Ray Lee
2006-11-21 18:05 ` Larry Finger
2006-11-21 18:32 ` Johannes Berg
2006-11-21 18:36 ` Johannes Berg
2006-11-21 18:49 ` Larry Finger
2006-11-22 13:58 ` Dan Williams [this message]
2006-11-22 17:11 ` Ray Lee
[not found] ` <200611210017.47695.mb@bu3sch.de>
[not found] ` <1164098989.2769.9.camel@ux156>
2006-11-21 8:59 ` Michael Buesch
[not found] ` <200611210959.17644.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-21 16:30 ` Larry Finger
2006-11-21 22:54 ` Michael Buesch
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=1164203890.3474.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--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 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.