a1a60635a8
The final check in this test case was issuing a new P2P_FIND command immediately after the P2P_SERVICE_DEL command on the peer. It looked like it was possible for the scan timing to go in a sequence that made the new P2P_FIND operation eventually accept a cfg80211 BSS entry from the very end of the previous P2P_FIND. This resulted in unexpected P2P-DEVICE-FOUND event even though there was no new Probe Response frame from the peer at that point in time. Make this less likely to show unrelated failures by waiting a bit before starting a new P2P_FIND operation after having changes peer configuration. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> |
||
|---|---|---|
| .. | ||
| ap-mgmt-fuzzer | ||
| eapol-fuzzer | ||
| hwsim | ||
| p2p-fuzzer | ||
| remote | ||
| wnm-fuzzer | ||
| .gitignore | ||
| Makefile | ||
| test-aes.c | ||
| test-asn1.c | ||
| test-base64.c | ||
| test-https.c | ||
| test-list.c | ||
| test-md4.c | ||
| test-milenage.c | ||
| test-rc4.c | ||
| test-rsa-sig-ver.c | ||
| test-sha1.c | ||
| test-sha256.c | ||
| test-x509.c | ||
| test-x509v3.c | ||
| test_x509v3_nist.sh | ||
| test_x509v3_nist2.sh | ||