mac80211: Send deauth/disassoc prior to dropping STA entry
RFC 1/1 mac80211: Send deauth/disassoc prior to dropping STA entry
Does this look fine or would there be better solution for reordering disconnections calls in a way that would allow us to maintain the keys needed to protect the deauth/disassoc frame?
When management frame protection (IEEE 802.11w) is used, the deauthentication and disassociation frames must be protected whenever the encryption keys are configured. We were removing the STA entry and with it, the keys, just before actually sending out these frames which meant that the frames went out unprotected. The AP will drop them in such a case. Fix this by reordering the operations a bit so that sta_info_destroy_addr() gets called only after ieee80211_send_deauth_disassoc().
--- net/mac80211/mlme.c | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-)
net/mac80211/mlme.c +14 -9
@@ -778,7 +778,8 @@ static void ieee80211_set_associated(strnetif_carrier_on (sdata->dev); } -static void ieee80211_set_disassoc (struct ieee80211_sub_if_data *sdata) +static void ieee80211_set_disassoc (struct ieee80211_sub_if_data *sdata, +int remove_sta) {struct ieee80211_if_managed *ifmgd = &sdata->u.mgd;struct ieee80211_local *local = sdata->local;
@@ -851,7 +852,8 @@ static void ieee80211_set_disassoc(struc changed |=BSS_CHANGED_BSSID ;ieee80211_bss_info_change_notify (sdata, changed); -sta_info_destroy_addr (sdata, bssid); +if (remove_sta) +sta_info_destroy_addr (sdata, bssid); } void ieee80211_sta_rx_notify(struct ieee80211_sub_if_data *sdata,
@@ -964,7 +966,7 @@ static void __ieee80211_connection_loss(printk (KERN_DEBUG "Connection to AP %pM lost.\n" , bssid); -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 );ieee80211_recalc_idle (local);mutex_unlock (&ifmgd->mtx);/*
@@ -1030,7 +1032,7 @@ ieee80211_rx_mgmt_deauth(struct ieee8021printk (KERN_DEBUG "%s: deauthenticated from %pM (Reason: %u)\n" , sdata->name, bssid, reason_code); -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 );ieee80211_recalc_idle (sdata->local);return RX_MGMT_CFG80211_DEAUTH ;
@@ -1060,7 +1062,7 @@ ieee80211_rx_mgmt_disassoc(struct ieee80printk (KERN_DEBUG "%s: disassociated from %pM (Reason: %u)\n" , sdata->name, mgmt->sa, reason_code); -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 );ieee80211_recalc_idle (sdata->local);return RX_MGMT_CFG80211_DISASSOC ; }
@@ -1708,7 +1710,7 @@ static void ieee80211_sta_work(struct woprintk (KERN_DEBUG "No probe response from AP %pM" " after %dms, disconnecting.\n" , bssid, (1000 *IEEE80211_PROBE_WAIT )/HZ ); -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 );ieee80211_recalc_idle (local);mutex_unlock (&ifmgd->mtx);/*
@@ -2010,7 +2012,7 @@ int ieee80211_mgd_assoc(struct ieee80211 }/* Trying to reassociate - clear previous association state */ -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 ); }mutex_unlock (&ifmgd->mtx);
@@ -2114,7 +2116,7 @@ int ieee80211_mgd_deauth(struct ieee8021if (ifmgd->associated == req->bss) { bssid = req->bss->bssid; -ieee80211_set_disassoc (sdata); +ieee80211_set_disassoc (sdata,1 );mutex_unlock (&ifmgd->mtx); }else {bool not_auth_yet = false;
@@ -2171,6 +2173,7 @@ int ieee80211_mgd_disassoc(struct ieee80 void *cookie) {struct ieee80211_if_managed *ifmgd = &sdata->u.mgd; +u8 bssid[ETH_ALEN ];mutex_lock (&ifmgd->mtx);
@@ -2188,13 +2191,15 @@ int ieee80211_mgd_disassoc(struct ieee80printk (KERN_DEBUG "%s: disassociating from %pM by local choice (reason=%d)\n" , sdata->name, req->bss->bssid, req->reason_code); -ieee80211_set_disassoc (sdata); +memcpy (bssid, req->bss->bssid,ETH_ALEN ); +ieee80211_set_disassoc (sdata,0 );mutex_unlock (&ifmgd->mtx);ieee80211_send_deauth_disassoc (sdata, req->bss->bssid,IEEE80211_STYPE_DISASSOC , req->reason_code, cookie); +sta_info_destroy_addr (sdata, bssid);ieee80211_recalc_idle (sdata->local);
Signature · 1 line
Jouni Malinen PGP id EFC895FA
Johannes Berg
maintainerQuoted 15 lines · Jouni Malinen
Does this look fine or would there be better solution for reordering disconnections calls in a way that would allow us to maintain the keys needed to protect the deauth/disassoc frame?
When management frame protection (IEEE 802.11w) is used, the deauthentication and disassociation frames must be protected whenever the encryption keys are configured. We were removing the STA entry and with it, the keys, just before actually sending out these frames which meant that the frames went out unprotected. The AP will drop them in such a case. Fix this by reordering the operations a bit so that
sta_info_destroy_addr()gets called only afterieee80211_send_deauth_disassoc().
net/mac80211/mlme.c static void ieee80211_set_associated(str · line 782
Quoted 3 lines
net/mac80211/mlme.c +2
-1-static void ieee80211_set_disassoc (struct ieee80211_sub_if_data *sdata) +static void ieee80211_set_disassoc (struct ieee80211_sub_if_data *sdata, +int remove_sta)
bool?
Other than that I think it looks fine, although I'm having second thoughts about the _existing_ ordering of the driver config calls there, but that's not something that this patch affects now, so it should be fine until we find out in the future that it's bad for some driver and we need to fix it, in which case we'll have to come up with an idea then :)
johannes