public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	linville@tuxdriver.com, johannes@sipsolutions.net,
	stable@kernel.org
Subject: Re: [PATCH] ath9k: fix keycache leak in split tkip case
Date: Tue, 9 Feb 2010 09:36:12 +0800	[thread overview]
Message-ID: <20100209093612.08d9ae17@tom-lei> (raw)
In-Reply-To: <43e72e891002081338q466d9747p10a61b5e1aca4c6d@mail.gmail.com>

>From 67b0faf7e7a57c3e6a971ff43d1f03f8e939429b Mon Sep 17 00:00:00 2001
From: Ming Lei <tom.leiming@gmail.com>
Date: Sat, 6 Feb 2010 22:30:53 +0800
Subject: [PATCH] ath9k: fix keycache leak in split tkip case

If split tkip key is used, ath_delete_key should delete
rx key and rx mic key. This patch fixes the leak of hw
keycache in the case.

---
The patch is against the latest wireless test tree.

Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Cc: stable@kernel.org
---
 drivers/net/wireless/ath/ath9k/main.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c
index 6796d5c..928402b 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -809,6 +809,7 @@ static void ath_key_delete(struct ath_common *common, struct ieee80211_key_conf
 
 	clear_bit(key->hw_key_idx + 64, common->keymap);
 	if (common->splitmic) {
+		ath9k_hw_keyreset(ah, key->hw_key_idx + 32);
 		clear_bit(key->hw_key_idx + 32, common->keymap);
 		clear_bit(key->hw_key_idx + 64 + 32, common->keymap);
 	}
-- 
1.6.2.5




On Mon, 8 Feb 2010 13:38:02 -0800
"Luis R. Rodriguez" <lrodriguez@atheros.com> wrote:

> On Sat, Feb 6, 2010 at 6:38 AM,  <tom.leiming@gmail.com> wrote:
> > From: Ming Lei <tom.leiming@gmail.com>
> >
> > If split tkip key is used, ath_delete_key should delete
> > rx key and rx mic key. This patch fixes the leak of hw
> > keycache in the case.
> 
> Can you please resend with Cc: stable@kernel.org on the commit log
> entry?
> 
> > ---
> > The patch is against the latest wireless test tree.
> >
> > Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> 
>   Luis


  reply	other threads:[~2010-02-09  1:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 14:38 [PATCH] ath9k: fix keycache leak in split tkip case tom.leiming
2010-02-08  9:20 ` [ath9k-devel] can ath9k run on linux 2.6.25 Zhang Yanfei-B21500
2010-02-08 18:01   ` Luis R. Rodriguez
2010-02-09  6:10     ` Jinsung Lee
2010-02-09  6:16       ` Luis R. Rodriguez
     [not found]       ` <25E8B46727291E4EB5A1CB88CBC4284E0100A779@zmy16exm21.fsl.freescale.net>
2010-02-09 17:10         ` Luis R. Rodriguez
2010-02-11  3:03           ` Zhang Yanfei-B21500
2010-02-13  1:28             ` Luis R. Rodriguez
2010-02-08 21:38 ` [PATCH] ath9k: fix keycache leak in split tkip case Luis R. Rodriguez
2010-02-09  1:36   ` Ming Lei [this message]
2010-02-09  7:51     ` Johannes Berg
2010-02-09 14:30       ` Ming Lei

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=20100209093612.08d9ae17@tom-lei \
    --to=tom.leiming@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@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