summaryrefslogtreecommitdiff
path: root/drivers/scsi/ncr53c8xx.c
diff options
context:
space:
mode:
authorLuca Pesce <luca.pesce@vimar.com>2020-12-24 11:51:59 +0100
committerKalle Valo <kvalo@codeaurora.org>2021-01-14 19:32:32 +0200
commite862a3e4088070de352fdafe9bd9e3ae0a95a33c (patch)
tree9c521820732f9ae840a6e36ec903cb915be11562 /drivers/scsi/ncr53c8xx.c
parent73c655410181b7fc9a5ff321a5021a684ada99e7 (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 <luca.pesce@vimar.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> Link: https://lore.kernel.org/r/1608807119-21785-1-git-send-email-luca.pesce@vimar.com
Diffstat (limited to 'drivers/scsi/ncr53c8xx.c')
0 files changed, 0 insertions, 0 deletions