| commit | 11432379fd2a3854a3408424d8dcd99afd811573 | |
| author | Helmut Schaa <helmut.schaa@googlemail.com> | |
| Thu, 12 Mar 2009 13:04:34 +0000 (12 14:04 +0100) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Sat, 28 Mar 2009 00:12:45 +0000 (27 20:12 -0400) | ||
| tree | c9184c78051ef76d9e9e148d2bc6777a10f02ca7 | treesnapshot (tar.gz zip) |
| parent | 51b381479ff5bc9b8c49ce15fd8bc35c6b695ca4 | commitdiff |
mac80211: start pending scan after probe/auth/assoc timed out
If a scan is queued in STA mode while the interface is in state direct
probe, authenticate or associate the scan is delayed until the interface
enters disabled or associated state. But in case of direct probe-,
authentication- or association- timeout sta_work will not be scheduled
anymore (without external trigger) and thus the pending scan is not
executed and prevents a new scan from being triggered (-EBUSY).
Fix this by queueing the sta work again after direct probe-, authentication-
and association- timeout.
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
If a scan is queued in STA mode while the interface is in state direct
probe, authenticate or associate the scan is delayed until the interface
enters disabled or associated state. But in case of direct probe-,
authentication- or association- timeout sta_work will not be scheduled
anymore (without external trigger) and thus the pending scan is not
executed and prevents a new scan from being triggered (-EBUSY).
Fix this by queueing the sta work again after direct probe-, authentication-
and association- timeout.
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/mac80211/mlme.c | diffblobblamehistory |