WPS: Make sure reconfiguration timeout is not left behind on deinit
Even though this is a short timeout, it is at least theoretically possible for the interface to be removed while waiting for reconfiguration to start. Avoid issues with this by cancelling the timeout on any WPS interface deinit. In theory, this should be postponed until interface removal, but that does not fit very nicely to the current wps_hostapd.c style. Signed-hostap: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
38ae43de6b
commit
0e22b8dd4c
1 changed files with 1 additions and 0 deletions
|
@ -1240,6 +1240,7 @@ void hostapd_deinit_wps(struct hostapd_data *hapd)
|
||||||
{
|
{
|
||||||
eloop_cancel_timeout(hostapd_wps_reenable_ap_pin, hapd, NULL);
|
eloop_cancel_timeout(hostapd_wps_reenable_ap_pin, hapd, NULL);
|
||||||
eloop_cancel_timeout(hostapd_wps_ap_pin_timeout, hapd, NULL);
|
eloop_cancel_timeout(hostapd_wps_ap_pin_timeout, hapd, NULL);
|
||||||
|
eloop_cancel_timeout(wps_reload_config, hapd->iface, NULL);
|
||||||
if (hapd->wps == NULL)
|
if (hapd->wps == NULL)
|
||||||
return;
|
return;
|
||||||
#ifdef CONFIG_WPS_UPNP
|
#ifdef CONFIG_WPS_UPNP
|
||||||
|
|
Loading…
Reference in a new issue