From: Jouni Malinen <j@w1.fi>
Date: Sat, 27 Dec 2014 13:37:13 +0000 (+0200)
Subject: Clear next_scan_freqs on wpa_supplicant FLUSH command
X-Git-Tag: hostap_2_4~643
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b8db1dfc5ca85b3443dab7757853b68687921d8e;p=thirdparty%2Fhostap.git

Clear next_scan_freqs on wpa_supplicant FLUSH command

It was possible for old scan state to remain from a previous test case
when an operation like WNM neighbor scan or another-BSS-in-ESS was
started, but stopped at the end of a test case. This could result in
failures, e.g., when running wnm_bss_tm_req followed by scan_setband.

Signed-off-by: Jouni Malinen <j@w1.fi>
---

diff --git a/wpa_supplicant/ctrl_iface.c b/wpa_supplicant/ctrl_iface.c
index e47a82c9c..29177484f 100644
--- a/wpa_supplicant/ctrl_iface.c
+++ b/wpa_supplicant/ctrl_iface.c
@@ -6057,6 +6057,8 @@ static void wpa_supplicant_ctrl_iface_flush(struct wpa_supplicant *wpa_s)
 #endif /* CONFIG_TESTING_OPTIONS */
 
 	wpa_s->disconnected = 0;
+	os_free(wpa_s->next_scan_freqs);
+	wpa_s->next_scan_freqs = NULL;
 }