P2P: Fix a race condition in some P2P command sequencies
The p2p->drv_in_listen variable is used to track Listen state operations in the driver. This is cleared when the driver reports that the Listen state has ended (p2p_listen_end() gets called). However, it is possible that the driver does not indicate that if the Listen state is canceled. This can apparently happen in some cases where p2p_connect command is issues while the Listen state is in progress. Work around this issue by clearing p2p->drv_in_listen when Listen state is stopped as part of p2p_stop operation. This allows the P2P module to process CONNECT_LISTEN timeout in p2p_timeout_connect_listen() to move to CONNECT state, e.g., when starting GO Negotiation after Device Discoverability mechanism.
This commit is contained in:
parent
6a5200e699
commit
54b8f99454
1 changed files with 10 additions and 0 deletions
|
@ -929,6 +929,16 @@ void p2p_stop_find_for_freq(struct p2p_data *p2p, int freq)
|
|||
"since we are on correct channel for response");
|
||||
return;
|
||||
}
|
||||
if (p2p->drv_in_listen) {
|
||||
/*
|
||||
* The driver may not deliver callback to p2p_listen_end()
|
||||
* when the operation gets canceled, so clear the internal
|
||||
* variable that is tracking driver state.
|
||||
*/
|
||||
wpa_msg(p2p->cfg->msg_ctx, MSG_DEBUG, "P2P: Clear "
|
||||
"drv_in_listen (%d)", p2p->drv_in_listen);
|
||||
p2p->drv_in_listen = 0;
|
||||
}
|
||||
p2p->cfg->stop_listen(p2p->cfg->cb_ctx);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue