Interworking: Start ANQP fetch from eloop callback
Reduce maximum stack use by starting next ANQP fetch operation from an eloop callback rather than calling interworking_next_anqp_fetch() directly from interworking_start_fetch_anqp(). This avoids issues that could potentially make the process run out of stack if long loops of ANQP operations are executed in cases where automatic Interworking network selection is used and scan results do not have a full match for a network. Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
6ace81ea77
commit
edd5939a26
1 changed files with 6 additions and 1 deletions
|
@ -2556,7 +2556,12 @@ void interworking_start_fetch_anqp(struct wpa_supplicant *wpa_s)
|
|||
bss->flags &= ~WPA_BSS_ANQP_FETCH_TRIED;
|
||||
|
||||
wpa_s->fetch_anqp_in_progress = 1;
|
||||
interworking_next_anqp_fetch(wpa_s);
|
||||
|
||||
/*
|
||||
* Start actual ANQP operation from eloop call to make sure the loop
|
||||
* does not end up using excessive recursion.
|
||||
*/
|
||||
eloop_register_timeout(0, 0, interworking_continue_anqp, wpa_s, NULL);
|
||||
}
|
||||
|
||||
|
||||
|
|
Loading…
Reference in a new issue