diff options
author | Chaitanya Tata <chaitanya.tata@bluwireless.co.uk> | 2019-05-01 15:55:24 +0300 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2019-05-28 10:35:39 +0300 |
commit | a3ce17d1495b65d62fceb2c7a704bb97133c5de9 (patch) | |
tree | d9dc6949a0dc8ad884a344b0d5cd71e662ab95e7 /certs | |
parent | cec4f328c929f72ad634e8f385b589bd6eac80e5 (diff) | |
download | linux-a3ce17d1495b65d62fceb2c7a704bb97133c5de9.tar.xz |
cfg80211: Handle bss expiry during connection
If the BSS is expired during connection, the connect result will
trigger a kernel warning. Ideally cfg80211 should hold the BSS
before the connection is attempted, but as the BSSID is not known
in case of auth/assoc MLME offload (connect op) it doesn't.
For those drivers without the connect op cfg80211 holds down the
reference so it wil not be removed from list.
Fix this by removing the warning and silently adding the BSS back to
the bss list which is return by the driver (with proper BSSID set) or
in case the BSS is already added use that.
The requirements for drivers are documented in the API's.
Signed-off-by: Chaitanya Tata <chaitanya.tata@bluwireless.co.uk>
[formatting fixes, keep old timestamp]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions