diff options
Diffstat (limited to 'net/wireless/mlme.c')
| -rw-r--r-- | net/wireless/mlme.c | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/net/wireless/mlme.c b/net/wireless/mlme.c index 1001db4912f7..82e6002c8d67 100644 --- a/net/wireless/mlme.c +++ b/net/wireless/mlme.c | |||
| @@ -93,7 +93,18 @@ void cfg80211_send_rx_assoc(struct net_device *dev, const u8 *buf, size_t len) | |||
| 93 | } | 93 | } |
| 94 | } | 94 | } |
| 95 | 95 | ||
| 96 | WARN_ON(!bss); | 96 | /* |
| 97 | * We might be coming here because the driver reported | ||
| 98 | * a successful association at the same time as the | ||
| 99 | * user requested a deauth. In that case, we will have | ||
| 100 | * removed the BSS from the auth_bsses list due to the | ||
| 101 | * deauth request when the assoc response makes it. If | ||
| 102 | * the two code paths acquire the lock the other way | ||
| 103 | * around, that's just the standard situation of a | ||
| 104 | * deauth being requested while connected. | ||
| 105 | */ | ||
| 106 | if (!bss) | ||
| 107 | goto out; | ||
| 97 | } else if (wdev->conn) { | 108 | } else if (wdev->conn) { |
| 98 | cfg80211_sme_failed_assoc(wdev); | 109 | cfg80211_sme_failed_assoc(wdev); |
| 99 | /* | 110 | /* |
