summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/ath/ath.h
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2010-08-28 16:21:21 (GMT)
committerJohn W. Linville <linville@tuxdriver.com>2010-08-31 18:22:23 (GMT)
commit56363ddeeed3afc5277ca227209773bc1042cc7b (patch)
tree2f92621e743983cb10175bbbd009ae2e167d1054 /drivers/net/wireless/ath/ath.h
parent3653910714a4a9b19aadb202c24f7b1ae61d3556 (diff)
downloadlinux-56363ddeeed3afc5277ca227209773bc1042cc7b.tar.xz
ath9k: fix spurious MIC failure reports
According to the hardware documentation, the MIC failure bit is only valid if the frame was decrypted using a valid TKIP key and is not a fragment. In some setups I've seen hardware-reported MIC failures on an AP that was configured for CCMP only, so it's clear that additional checks are necessary. Signed-off-by: Felix Fietkau <nbd@openwrt.org> Cc: stable@kernel.org Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/ath/ath.h')
-rw-r--r--drivers/net/wireless/ath/ath.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath.h b/drivers/net/wireless/ath/ath.h
index d32f282..a706202 100644
--- a/drivers/net/wireless/ath/ath.h
+++ b/drivers/net/wireless/ath/ath.h
@@ -119,6 +119,7 @@ struct ath_common {
u32 keymax;
DECLARE_BITMAP(keymap, ATH_KEYMAX);
+ DECLARE_BITMAP(tkip_keymap, ATH_KEYMAX);
u8 splitmic;
struct ath_regulatory regulatory;