aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/dbus/dbus_new_handlers.c
diff options
context:
space:
mode:
authorMasashi Honma <masashi.honma@gmail.com>2019-01-15 11:43:41 (GMT)
committerJouni Malinen <j@w1.fi>2019-01-21 21:43:12 (GMT)
commit3e949655ccc5fba4686d04c70380463ebf059b30 (patch)
tree318bd2cfd7ff522051c9024f43d7d8a4f8545bcb /wpa_supplicant/dbus/dbus_new_handlers.c
parent9758b08bcf9acb98db2db8a1407b5546d44f907b (diff)
downloadhostap-3e949655ccc5fba4686d04c70380463ebf059b30.zip
hostap-3e949655ccc5fba4686d04c70380463ebf059b30.tar.gz
hostap-3e949655ccc5fba4686d04c70380463ebf059b30.tar.bz2
Revert "mesh: Apply channel attributes before setup interface"
This reverts commit 2564184440d9d6041d11a8c7d50b31368634c3bd. Commit 2564184440d9 ("mesh: Apply channel attributes before setup interface") triggers some channel configurations to result in leaking memory. This seems to be caused by hapd->started not getting set when going through a callback to start hostapd operation (e.g., when using HT40 coex scan) due to hostapd_setup_bss() not getting called. This results in hostapd_free_hapd_data() not clearing allocated hapd->wpa_auth. This can be reproduced with the hwsim test case mesh_secure_ocv_mix_legacy. A more complete cleanup of the pending mesh patch for DFS support seems to be needed to fix this properly, so the best approach for now is to revert this patch and bring it back once rest of the mesh changes are ready to be applied. Signed-off-by: Masashi Honma <masashi.honma@gmail.com>
Diffstat (limited to 'wpa_supplicant/dbus/dbus_new_handlers.c')
0 files changed, 0 insertions, 0 deletions