diff options
| author | Luca Pesce <[email protected]> | 2020-12-24 11:51:59 +0100 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2021-01-14 19:32:32 +0200 |
| commit | e862a3e4088070de352fdafe9bd9e3ae0a95a33c (patch) | |
| tree | 9c521820732f9ae840a6e36ec903cb915be11562 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 73c655410181b7fc9a5ff321a5021a684ada99e7 (diff) | |
brcmfmac: clear EAP/association status bits on linkdown events
This ensure that previous association attempts do not leave stale statuses
on subsequent attempts.
This fixes the WARN_ON(!cr->bss)) from __cfg80211_connect_result() when
connecting to an AP after a previous connection failure (e.g. where EAP fails
due to incorrect psk but association succeeded). In some scenarios, indeed,
brcmf_is_linkup() was reporting a link up event too early due to stale
BRCMF_VIF_STATUS_ASSOC_SUCCESS bit, thus reporting to cfg80211 a connection
result with a zeroed bssid (vif->profile.bssid is still empty), causing the
WARN_ON due to the call to cfg80211_get_bss() with the empty bssid.
Signed-off-by: Luca Pesce <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions