linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Senthil Balasubramanian <senthilkumar@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Stable <stable@kernel.org>
Subject: Re: [PATCH v3 2/2] ath9k: Fix STA disconnect issue due to received MIC failed bcast frames
Date: Fri, 31 Dec 2010 09:19:41 -0800	[thread overview]
Message-ID: <4D1E10AD.4090703@candelatech.com> (raw)
In-Reply-To: <1291642767-11939-1-git-send-email-senthilkumar@atheros.com>

On 12/06/2010 05:39 AM, Senthil Balasubramanian wrote:
> AR_RxKeyIdxValid will not be set for bcast/mcast frames and so relying
> this status for MIC failed frames is buggy.
>
> Due to this, MIC failure events for broadcast frames are not sent to
> supplicant resulted in AP disconnecting the STA.
>
> Able to pass Wifi Test case 5.2.18 with this fix.

Did this ever make it into wireless-testing?  I just did
a rebase, and I notice I'm still carrying this patch in my
local tree?

Thanks,
Ben

>
> Cc: Stable<stable@kernel.org>  (2.6.36+)
> Signed-off-by: Senthil Balasubramanian<senthilkumar@atheros.com>
> ---
> v2 -- addressed invalid keyix overrun in tkip_keymap.
> v3 -- fixed setting of rx decrypted flag in case of s/w crypto.
>
>   drivers/net/wireless/ath/ath9k/mac.c  |    3 +--
>   drivers/net/wireless/ath/ath9k/recv.c |    9 ++++++++-
>   2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/mac.c b/drivers/net/wireless/ath/ath9k/mac.c
> index b04b37b..7978b27 100644
> --- a/drivers/net/wireless/ath/ath9k/mac.c
> +++ b/drivers/net/wireless/ath/ath9k/mac.c
> @@ -702,8 +702,7 @@ int ath9k_hw_rxprocdesc(struct ath_hw *ah, struct ath_desc *ds,
>   			rs->rs_phyerr = phyerr;
>   		} else if (ads.ds_rxstatus8&  AR_DecryptCRCErr)
>   			rs->rs_status |= ATH9K_RXERR_DECRYPT;
> -		else if ((ads.ds_rxstatus8&  AR_MichaelErr)&&
> -		         rs->rs_keyix != ATH9K_RXKEYIX_INVALID)
> +		else if (ads.ds_rxstatus8&  AR_MichaelErr)
>   			rs->rs_status |= ATH9K_RXERR_MIC;
>   		else if (ads.ds_rxstatus8&  AR_KeyMiss)
>   			rs->rs_status |= ATH9K_RXERR_DECRYPT;
> diff --git a/drivers/net/wireless/ath/ath9k/recv.c b/drivers/net/wireless/ath/ath9k/recv.c
> index 262c815..876aa8f 100644
> --- a/drivers/net/wireless/ath/ath9k/recv.c
> +++ b/drivers/net/wireless/ath/ath9k/recv.c
> @@ -840,6 +840,10 @@ static bool ath9k_rx_accept(struct ath_common *common,
>   			    struct ath_rx_status *rx_stats,
>   			    bool *decrypt_error)
>   {
> +#define is_mc_or_valid_tkip_keyix ((is_mc ||			\
> +		(rx_stats->rs_keyix != ATH9K_RXKEYIX_INVALID&&  \
> +		test_bit(rx_stats->rs_keyix, common->tkip_keymap))))
> +
>   	struct ath_hw *ah = common->ah;
>   	__le16 fc;
>   	u8 rx_status_len = ah->caps.rx_status_len;
> @@ -881,15 +885,18 @@ static bool ath9k_rx_accept(struct ath_common *common,
>   		if (rx_stats->rs_status&  ATH9K_RXERR_DECRYPT) {
>   			*decrypt_error = true;
>   		} else if (rx_stats->rs_status&  ATH9K_RXERR_MIC) {
> +			bool is_mc;
>   			/*
>   			 * The MIC error bit is only valid if the frame
>   			 * is not a control frame or fragment, and it was
>   			 * decrypted using a valid TKIP key.
>   			 */
> +			is_mc = !!is_multicast_ether_addr(hdr->addr1);
> +
>   			if (!ieee80211_is_ctl(fc)&&
>   			!ieee80211_has_morefrags(fc)&&
>   			!(le16_to_cpu(hdr->seq_ctrl)&  IEEE80211_SCTL_FRAG)&&
> -			    test_bit(rx_stats->rs_keyix, common->tkip_keymap))
> +			    is_mc_or_valid_tkip_keyix)
>   				rxs->flag |= RX_FLAG_MMIC_ERROR;
>   			else
>   				rx_stats->rs_status&= ~ATH9K_RXERR_MIC;


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2010-12-31 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 13:39 [PATCH v3 2/2] ath9k: Fix STA disconnect issue due to received MIC failed bcast frames Senthil Balasubramanian
2010-12-31 17:19 ` Ben Greear [this message]
2011-01-03 10:18   ` Senthil Balasubramanian

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=4D1E10AD.4090703@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=senthilkumar@atheros.com \
    --cc=stable@kernel.org \
    /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).