linux-kernel - Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Nov 2006 08:58:10 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Ray Lee <ray-lk@...rabbit.org>,
	Broadcom Linux <bcm43xx-dev@...ts.berlios.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant
	-	NetworkManager deadlock

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/