| commit | b4a82a0a2e32777267b2c997fa55b90056447a40 | |
| author | Felix Fietkau <nbd@openwrt.org> | |
| Sat, 14 Jan 2012 14:08:34 +0000 (14 15:08 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Thu, 26 Jan 2012 00:13:55 +0000 (25 16:13 -0800) | ||
| tree | 2c8a79a3709a034faa78cd7861dfd3c3ff847872 | treesnapshot (tar.gz zip) |
| parent | ebd11e15ac4b85124de9f41c335bd3b00661e49d | commitdiff |
ath9k_hw: fix interpretation of the rx KeyMiss flag
commit 7a532fe7131216a02c81a6c1b1f8632da1195a58 upstream.
Documentation states that the KeyMiss flag is only valid if RxFrameOK is
unset, however empirical evidence has shown that this is false.
When KeyMiss is set (and RxFrameOK is 1), the hardware passes a valid frame
which has not been decrypted. The driver then falsely marks the frame
as decrypted, and when using CCMP this corrupts the rx CCMP PN, leading
to connection hangs.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 7a532fe7131216a02c81a6c1b1f8632da1195a58 upstream.
Documentation states that the KeyMiss flag is only valid if RxFrameOK is
unset, however empirical evidence has shown that this is false.
When KeyMiss is set (and RxFrameOK is 1), the hardware passes a valid frame
which has not been decrypted. The driver then falsely marks the frame
as decrypted, and when using CCMP this corrupts the rx CCMP PN, leading
to connection hangs.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/net/wireless/ath/ath9k/ar9003_mac.c | diffblobblamehistory | |
| drivers/net/wireless/ath/ath9k/mac.c | diffblobblamehistory |