diff options
| author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2015-08-17 15:54:41 +0300 |
|---|---|---|
| committer | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2015-08-18 10:25:26 +0300 |
| commit | ecc7c518b3017821a6b26fb5fdaa548afa8ee236 (patch) | |
| tree | e5a4f37d87933dec534bce6b915c394025489c1e /drivers/net/wireless/iwlwifi/iwl-phy-db.h | |
| parent | b3df22475423a99cc1f6c4b202970fa89a4d9716 (diff) | |
| download | kernel_replicant_linux-ecc7c518b3017821a6b26fb5fdaa548afa8ee236.tar.gz kernel_replicant_linux-ecc7c518b3017821a6b26fb5fdaa548afa8ee236.tar.bz2 kernel_replicant_linux-ecc7c518b3017821a6b26fb5fdaa548afa8ee236.zip | |
iwlwifi: mvm: fix a race in D0i3 vs. Tx path
When we enter D0i3, we must stop TXing otherwise the
sequence number we use might conflict with the firmware's
internal TX. In order to do so, we have
IWL_MVM_STATUS_IN_D0I3 which should prevent any Tx while we
enter D0i3. There is a bug in this code since we may Tx even
if IWL_MVM_STATUS_IN_D0I3 is set. This can happen as long as
mvm->d0i3_ap_sta_id is not set.
To make sure that we don't have any packet in the Tx path
while we set mvm->d0i3_ap_sta_id, call synchronize_net only
after we already set mvm->d0i3_ap_sta_id.
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'drivers/net/wireless/iwlwifi/iwl-phy-db.h')
0 files changed, 0 insertions, 0 deletions