renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-30 16:13:54 +08:00
Code

mac80211: respond to beacon loss report only once

Browse Source 
The driver might keep reporting beacon loss until we
disassociate -- catch that and don't respond to any
subsequent events until the probe is either successful
or we disassociate.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
Johannes Berg 2009-05-12 19:58:12 +02:00 committed by John W. Linville
parent f7eef3563c
commit 34bfc411f6
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
net/mac80211/mlme.c
View File

@ -1182,6 +1182,17 @@ void ieee80211_beacon_loss_work(struct work_struct *work)
u.mgd.beacon_loss_work); u.mgd.beacon_loss_work);
struct ieee80211_if_managed *ifmgd = &sdata->u.mgd; struct ieee80211_if_managed *ifmgd = &sdata->u.mgd;
/*
* The driver has already reported this event and we have
* already sent a probe request. Maybe the AP died and the
* driver keeps reporting until we disassociate... We have
* to ignore that because otherwise we would continually
* reset the timer and never check whether we received a
* probe response!
*/
if (ifmgd->flags & IEEE80211_STA_PROBEREQ_POLL)
return;
#ifdef CONFIG_MAC80211_VERBOSE_DEBUG #ifdef CONFIG_MAC80211_VERBOSE_DEBUG
if (net_ratelimit()) { if (net_ratelimit()) {
printk(KERN_DEBUG "%s: driver reports beacon loss from AP %pM " printk(KERN_DEBUG "%s: driver reports beacon loss from AP %pM "