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. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- From: Larry Finger <Larry.Finger@lwfinger.net>
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- References:
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- From: Ray Lee <ray-lk@madrabbit.org>
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- From: Larry Finger <Larry.Finger@lwfinger.net>
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- From: Johannes Berg <johannes@sipsolutions.net>
- Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- Prev by Date: -mm: please drop reiser4-export-handle_ra_miss.patch
- Next by Date: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- Previous by thread: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- Next by thread: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
- Index(es):
![]() |