From b8db1dfc5ca85b3443dab7757853b68687921d8e Mon Sep 17 00:00:00 2001 From: Jouni Malinen Date: Sat, 27 Dec 2014 15:37:13 +0200 Subject: [PATCH] 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 --- wpa_supplicant/ctrl_iface.c | 2 ++ 1 file changed, 2 insertions(+) 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; }