ath10k: fix locking for WEP keys
peer->keys needs to be protected by data_lock since it is also accessed from the WMI path. Both install() and clear() routines for peer keys modify the key contents, so use the data_lock to avoid races. Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
This commit is contained in:

committed by
Kalle Valo

parent
504f6cdf4a
commit
ae1671318e
@@ -136,7 +136,9 @@ static int ath10k_install_peer_wep_keys(struct ath10k_vif *arvif,
|
||||
if (ret)
|
||||
return ret;
|
||||
|
||||
spin_lock_bh(&ar->data_lock);
|
||||
peer->keys[i] = arvif->wep_keys[i];
|
||||
spin_unlock_bh(&ar->data_lock);
|
||||
}
|
||||
|
||||
return 0;
|
||||
@@ -173,7 +175,9 @@ static int ath10k_clear_peer_keys(struct ath10k_vif *arvif,
|
||||
ath10k_warn(ar, "failed to remove peer wep key %d: %d\n",
|
||||
i, ret);
|
||||
|
||||
spin_lock_bh(&ar->data_lock);
|
||||
peer->keys[i] = NULL;
|
||||
spin_unlock_bh(&ar->data_lock);
|
||||
}
|
||||
|
||||
return first_errno;
|
||||
|
Reference in New Issue
Block a user