From: Greg KH <greg@kroah.com>
To: Vivek Natarajan <vnatarajan@Atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
stable@kernel.org, Ranga Rao Ravuri <ranga.ravuri@Atheros.com>
Subject: Re: [stable] [PATCH 2/2] ath9k: Avoid corrupt frames being forwarded to mac80211.
Date: Thu, 3 Jun 2010 15:17:51 -0700 [thread overview]
Message-ID: <20100603221751.GB22595@kroah.com> (raw)
In-Reply-To: <1272353738-17084-2-git-send-email-vnatarajan@atheros.com>
On Tue, Apr 27, 2010 at 01:05:38PM +0530, Vivek Natarajan wrote:
> If bit 29 is set, MAC H/W can attempt to decrypt the received aggregate
> with WEP or TKIP, eventhough the received frame may be a CRC failed
> corrupted frame. If this bit is set, H/W obeys key type in keycache.
> If it is not set and if the key type in keycache is neither open nor
> AES, H/W forces key type to be open. But bit 29 should be set to 1
> for AsyncFIFO feature to encrypt/decrypt the aggregate with WEP or TKIP.
>
> Cc: stable@kernel.org
> Reported-by: Johan Hovold <johan.hovold@lundinova.se>
> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
> Signed-off-by: Ranga Rao Ravuri <ranga.ravuri@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/ar5008_initvals.h | 2 +-
> drivers/net/wireless/ath/ath9k/ar9002_initvals.h | 8 ++++----
This is now upstream in Linus's tree, but does not apply to the .32,
.32, or .34 kernel trees due to the file movements in this area. I
tried to apply this by hand, but didn't get it correct.
Can someone please send me a properly backported version of this patch
to apply to the -stable tree?
thanks,
greg k-h
next prev parent reply other threads:[~2010-06-03 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 7:35 [PATCH 1/2] ath9k_htc: Handle CONF_IDLE during unassociated state to save power Vivek Natarajan
2010-04-27 7:35 ` [PATCH 2/2] ath9k: Avoid corrupt frames being forwarded to mac80211 Vivek Natarajan
2010-06-03 22:17 ` Greg KH [this message]
2010-06-03 22:52 ` [stable] " Luis R. Rodriguez
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=20100603221751.GB22595@kroah.com \
--to=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ranga.ravuri@Atheros.com \
--cc=stable@kernel.org \
--cc=vnatarajan@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