aboutsummaryrefslogtreecommitdiffstats
path: root/src/l2_packet
diff options
context:
space:
mode:
authorJouni Malinen <jouni@qca.qualcomm.com>2014-10-27 22:19:24 (GMT)
committerJouni Malinen <j@w1.fi>2014-10-27 22:43:58 (GMT)
commita7f5271d52e7aabf6c6aee54da2fdcb65df89cdc (patch)
tree110b782d31becaadaebe095d14ffb1a1844ff0c9 /src/l2_packet
parent1531402ee4888b28f85ce6333b0f6b7740675990 (diff)
downloadhostap-a7f5271d52e7aabf6c6aee54da2fdcb65df89cdc.zip
hostap-a7f5271d52e7aabf6c6aee54da2fdcb65df89cdc.tar.gz
hostap-a7f5271d52e7aabf6c6aee54da2fdcb65df89cdc.tar.bz2
Update pending connect radio work BSS pointer on scan update
It is possible for scan result processing or BSS entry removal to occur while there is a pending connect or sme-connect radio work with a previously selected BSS entry. The BSS pointer was previously verified to be valid, i.e., still point to a BSS entry, at the time the actual connection operation is started. However, that BSS entry could have changed to point to another BSS if the old BSS entry was either removed or reallocated and a new BSS entry was added at the same location in memory. This could result in the connection attempt failing to configure parameters properly due to different BSS information (e.g., different BSSID). Fix this by updated the pending connect radio work data on BSS entry updates similarly to how the last_scan_res array was updated. If the selected BSS entry is removed, this will still result in a failed connection, but reallocated BSS entry is now followed properly and used when the connection work starts. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'src/l2_packet')
0 files changed, 0 insertions, 0 deletions