From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless@vger.kernel.org
Cc: lrodriguez@atheros.com, linville@tuxdriver.com
Subject: Re: [PATCH 7/7] ath9k_hw: handle an rx key miss properly
Date: Mon, 12 Jul 2010 11:20:32 +0200 [thread overview]
Message-ID: <4C3ADE60.3030309@openwrt.org> (raw)
In-Reply-To: <1278845325-62000-7-git-send-email-nbd@openwrt.org>
On 2010-07-11 12:48 PM, Felix Fietkau wrote:
> If the hardware reports an rx key miss, then the frame has not been
> decrypted at all, and this must be recognized by the software, otherwise
> mac80211 can generate bogus MIC failure events.
>
> Fix this by reporting an invalid key index if a key miss is detected
> in the rx status.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Cc: stable@kernel.org
Please ignore this patch, I'll send a v2 of it soon.
- Felix
prev parent reply other threads:[~2010-07-12 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 10:48 [PATCH 1/7] ath9k_hw: fix antenna diversity on AR9285 Felix Fietkau
2010-07-11 10:48 ` [PATCH 2/7] ath9k_hw: fix a sign error in the IQ calibration code Felix Fietkau
2010-07-11 10:48 ` [PATCH 3/7] ath9k_hw: fix an off-by-one error in the PDADC boundaries calculation Felix Fietkau
2010-07-11 10:48 ` [PATCH 4/7] ath9k_hw: prevent a fast channel change after a rx DMA stuck issue Felix Fietkau
2010-07-11 10:48 ` [PATCH 5/7] ath9k_hw: report the TID in the tx status on AR5008-AR9002 Felix Fietkau
2010-07-11 10:48 ` [PATCH 6/7] ath9k: validate the TID in the tx status information Felix Fietkau
2010-07-11 10:48 ` [PATCH 7/7] ath9k_hw: handle an rx key miss properly Felix Fietkau
2010-07-12 9:20 ` Felix Fietkau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3ADE60.3030309@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).