From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
651199@bugs.debian.org,
Andreas Gustafsson <olangu@impressions.se>,
Marco d'Itri <md@Linux.IT>,
Gabriel Kerneis <kerneis@pps.jussieu.fr>
Subject: Re: iwlwifi WPA-TKIP crypto failure after group rekeying
Date: Mon, 27 Feb 2012 05:59:38 -0800 [thread overview]
Message-ID: <1330351178.12612.3.camel@wwguy-huron> (raw)
In-Reply-To: <1330333354.3483.6.camel@jlt3.sipsolutions.net>
Hi Ben/Johannes,
On Mon, 2012-02-27 at 10:02 +0100, Johannes Berg wrote:
> Hi Ben,
>
> Thanks for the report.
>
> On Mon, 2012-02-27 at 05:33 +0000, Ben Hutchings wrote:
> > Several Debian users (cc'd) have reported a regression in iwlagn in
> > Linux 3.1, not fixed in 3.2. The full bug log is at:
> >
> > http://bugs.debian.org/651199
> >
> > To summarise, a WPA-TKIP managed connection stops passing traffic and
> > the kernel log shows the message "WPA: Group rekeying". This apparently
> > doesn't happen if the connection is in heavy use at the time or with
> > module parameter swcrypto=1. WPA2 is not affected either.
>
> I think this is due to my patch "iwlagn: rewrite HW crypto" which
> accidentally broke key *removal* (of all things), which causes issues
> when the first GTK is removed on the second rekeying.
>
> This patch
> http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=commitdiff;h=5dcbf480473f6c3f06ad2426b7517038a2a18911
>
> should fix it. Wey has sent it to John, but he hasn't picked it up yet
> for some reason -- it's also marked for stable.
>
> It'd be great to get confirmation that this is the problem, I'm not sure
> I'll find time today to reproduce the problem.
>
John merge the patch 5 days ago anf yuo can find it in wireless-testing
tree
authorJohannes Berg <johannes.berg@intel.com> Fri, 17 Feb 2012 17:47:14
+0000 (09:47 -0800) committerJohn W. Linville <linville@tuxdriver.com>
Tue, 21 Feb 2012 19:45:26 +0000 (14:45 -0500)
commit5dcbf480473f6c3f06ad2426b7517038a2a18911
tree66d2cbefee018ff46d499e0aeab573aa94558353tree | snapshot
parent7be081539e540517d5e1fcbf96b8080074afbf08commit | diff
Wey
>
next prev parent reply other threads:[~2012-02-27 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 5:33 iwlwifi WPA-TKIP crypto failure after group rekeying Ben Hutchings
2012-02-27 9:02 ` Johannes Berg
2012-02-27 13:59 ` Guy, Wey-Yi [this message]
2012-02-28 2:02 ` Jonathan Nieder
2012-03-05 4:53 ` Jonathan Nieder
2012-03-05 4:53 ` Jonathan Nieder
2012-03-05 6:52 ` Johannes Berg
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=1330351178.12612.3.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=651199@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=kerneis@pps.jussieu.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=md@Linux.IT \
--cc=olangu@impressions.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.