From: Johannes Berg <johannes.berg@intel.com>
Date: Sat, 19 Mar 2011 11:08:08 +0000 (+0200)
Subject: wpa_s AP mode: propagate scan event
X-Git-Tag: hostap-1-bp~464
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c202f19c682b5f87ba0259bea8449d6667f2e811;p=thirdparty%2Fhostap.git

wpa_s AP mode: propagate scan event

When wpa_s scans in AP mode, it doesn't propagate the scan event to the
AP code, so that code can get stuck if it uses the callbacks there.
Simply call them where appropriate.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---

diff --git a/wpa_supplicant/events.c b/wpa_supplicant/events.c
index fedf0cbd0..030dc60c6 100644
--- a/wpa_supplicant/events.c
+++ b/wpa_supplicant/events.c
@@ -903,6 +903,10 @@ static int _wpa_supplicant_event_scan_results(struct wpa_supplicant *wpa_s,
 
 	if (ap) {
 		wpa_dbg(wpa_s, MSG_DEBUG, "Ignore scan results in AP mode");
+#ifdef CONFIG_AP
+		if (wpa_s->ap_iface->scan_cb)
+			wpa_s->ap_iface->scan_cb(wpa_s->ap_iface);
+#endif /* CONFIG_AP */
 		wpa_scan_results_free(scan_res);
 		return 0;
 	}