Commit 34bfc411 authored by Johannes Berg's avatar Johannes Berg Committed by John W. Linville
Browse files

mac80211: respond to beacon loss report only once



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: default avatarJohannes Berg <johannes@sipsolutions.net>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent f7eef356
...@@ -1182,6 +1182,17 @@ void ieee80211_beacon_loss_work(struct work_struct *work) ...@@ -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 "
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment