P2P: Continue p2p_find after sending non-success Invitation Response
This was previously handled for the case where the non-success Invitation Response frame was sent out during the Listen phase. However, in the case the Action frame TX ended up getting scheduled when the Search phase scan had already started (e.g., due to the driver reporting Invitation Request RX late enough for the Listen-to-Search transition having already started), the postponed Action frame TX status processing did not cover the specific case of non-success Invitation Response. This could result in the p2p_find operation getting stopped (stuck in SEARCH state) unexpectedly. Fix this by calling p2p_check_after_scan_tx_continuation() from Invitation Response TX callback handler if the invitation was rejected. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
This commit is contained in:
parent
0f34665774
commit
3433721c5f
1 changed files with 2 additions and 0 deletions
|
@ -3782,6 +3782,8 @@ void p2p_send_action_cb(struct p2p_data *p2p, unsigned int freq, const u8 *dst,
|
||||||
break;
|
break;
|
||||||
case P2P_PENDING_INVITATION_RESPONSE:
|
case P2P_PENDING_INVITATION_RESPONSE:
|
||||||
p2p_invitation_resp_cb(p2p, success);
|
p2p_invitation_resp_cb(p2p, success);
|
||||||
|
if (p2p->inv_status != P2P_SC_SUCCESS)
|
||||||
|
p2p_check_after_scan_tx_continuation(p2p);
|
||||||
break;
|
break;
|
||||||
case P2P_PENDING_DEV_DISC_REQUEST:
|
case P2P_PENDING_DEV_DISC_REQUEST:
|
||||||
p2p_dev_disc_req_cb(p2p, success);
|
p2p_dev_disc_req_cb(p2p, success);
|
||||||
|
|
Loading…
Reference in a new issue