Am Montag, 9. März 2009 schrieb Helmut Schaa: > If cfg80211 requests a scan it awaits either a return code != 0 from > the scan function or the cfg80211_scan_done to be called. In case of > a STA mac80211's scan function ever returns 0 and queues the scan request. > If ieee80211_sta_work is executed and ieee80211_start_scan fails for > some reason cfg80211_scan_done will never be called but cfg80211 still > thinks the scan was triggered successfully and will refuse any future > scan requests due to drv->scan_req not being cleaned up. > > If a scan is triggered from within the MLME a similar problem appears. If > ieee80211_start_scan returns an error, local->scan_req will not be reset > and mac80211 will refuse any future scan requests. > > Hence, in both cases call ieee80211_scan_failed (which notifies cfg80211 > and resets local->scan_req) if ieee80211_start_scan returns an error. > > Signed-off-by: Helmut Schaa <helmut.schaa@xxxxxxxxxxxxxx> Btw, John, I guess this should go into linux-next as the cfg80211-scan code is there already and otherwise cfg80211 and mac80211 can get stuck (refuses any scan requests) when the iwlwifi killswitch is used (only tested with NetworkManager). I'm not sure if anything apart from the killswitch also triggers this issue. Thanks, Helmut -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
