| commit | 846d9363505d14e591a427619ccb7ffe6a7a3541 | |
| author | Felix Fietkau <nbd@openwrt.org> | |
| Sat, 8 Oct 2011 20:02:58 +0000 (8 22:02 +0200) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Tue, 11 Oct 2011 20:41:29 +0000 (11 16:41 -0400) | ||
| tree | ed8b1c7aa4eef315a700454ba243219e5ae75903 | treesnapshot (tar.gz zip) |
| parent | 1b428a26a13732444ca4c16914e03cfe878b15f4 | commitdiff |
ath9k_hw: fix a regression in key miss handling
The commit "ath9k_hw: Fix incorrect key_miss handling" changed the code
to only report key miss errors if a MIC error wasn't reported.
When checking the flags in that order in the MAC code, it might miss some
real events, because the value of the MIC error flag is undefined under
some conditions.
The primary issue addressed by the previous commit is making sure that
MIC errors are properly reported on the STA side. This can be fixed in
a better way by adding a separate rx status flag for key miss and
ignoring it for multicast frames.
This fix slightly improves stability in AP mode on some older hardware,
like AR9132.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The commit "ath9k_hw: Fix incorrect key_miss handling" changed the code
to only report key miss errors if a MIC error wasn't reported.
When checking the flags in that order in the MAC code, it might miss some
real events, because the value of the MIC error flag is undefined under
some conditions.
The primary issue addressed by the previous commit is making sure that
MIC errors are properly reported on the STA side. This can be fixed in
a better way by adding a separate rx status flag for key miss and
ignoring it for multicast frames.
This fix slightly improves stability in AP mode on some older hardware,
like AR9132.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>