From: Johannes Berg <johannes@sipsolutions.net>
To: Ming Lei <tom.leiming@gmail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
linville@tuxdriver.com, stable@kernel.org
Subject: Re: [PATCH] ath9k: fix keycache leak in split tkip case
Date: Tue, 09 Feb 2010 08:51:48 +0100 [thread overview]
Message-ID: <1265701908.3783.13.camel@johannes.berg> (raw)
In-Reply-To: <20100209093612.08d9ae17@tom-lei>
On Tue, 2010-02-09 at 09:36 +0800, Ming Lei wrote:
> 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
This is ordered wrong, it needs to be
----------
From: foo
If split ...
Signed-off-by: ...
Cc: stable...
---
The patch is against...
(everything after --- is removed from the commit log when committing)
----------
johannes
next prev parent reply other threads:[~2010-02-09 7:52 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
2010-02-09 7:51 ` Johannes Berg [this message]
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=1265701908.3783.13.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=stable@kernel.org \
--cc=tom.leiming@gmail.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