summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBen Greear <greearb@candelatech.com>2013-03-25 19:19:35 +0100
committerJohannes Berg <johannes.berg@intel.com>2013-04-08 09:16:55 +0200
commita13fbe549fded5b77e020d4e08f1f74e212cc543 (patch)
tree13a549e4be020dd4d782b840f8c87bc5c945cc51
parentmac80211: add beacon stats to debugfs (diff)
downloadlinux-a13fbe549fded5b77e020d4e08f1f74e212cc543.tar.xz
linux-a13fbe549fded5b77e020d4e08f1f74e212cc543.zip
mac80211: be more careful about sending beacon-loss-events
I don't think we should send the events unless it was actually a beacon that was lost...not just any probe of an AP. Signed-off-by: Ben Greear <greearb@candelatech.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to '')
-rw-r--r--net/mac80211/mlme.c8
1 files changed, 5 insertions, 3 deletions
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 237e2ef42ba9..e12fedcfa988 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -1988,13 +1988,15 @@ static void ieee80211_mgd_probe_ap(struct ieee80211_sub_if_data *sdata,
goto out;
}
- if (beacon)
+ if (beacon) {
mlme_dbg_ratelimited(sdata,
"detected beacon loss from AP (missed %d beacons) - probing\n",
beacon_loss_count);
- ieee80211_cqm_rssi_notify(&sdata->vif,
- NL80211_CQM_RSSI_BEACON_LOSS_EVENT, GFP_KERNEL);
+ ieee80211_cqm_rssi_notify(&sdata->vif,
+ NL80211_CQM_RSSI_BEACON_LOSS_EVENT,
+ GFP_KERNEL);
+ }
/*
* The driver/our work has already reported this event or the