From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Bob Copeland <bcopeland@gmail.com>
Subject: Re: [PATCH] mac80211: re-upload keys only after telling driver about association
Date: Fri, 10 Apr 2009 09:29:16 +0200 [thread overview]
Message-ID: <1239348556.17031.14.camel@johannes.local> (raw)
In-Reply-To: <1239294389.4684.15.camel@rc-desk>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hi,
> On Tue, 2009-04-07 at 17:55 -0700, Johannes Berg wrote:
> > In the normal WPA or RSN case keys are only configured after
> > associating, so we should do that in that order when resuming
> > as well. It shouldn't really matter since we do not send any
> > data at either point, but iwlwifi prefers it this way and it
> > does seem more natural.
>
> Could you please share the symptom of the problem with iwlwifi without
> this patch?
[this is just a snippet from my other mail -- for the wider audience]
When you have a microcode error, we pretty much take the driver
completely down, and the firmware is of course completely
re-initialised. Now, when mac80211 goes to reconfigure the hardware, it
would, before this patch, do this [simplified, but you can look at the
code]:
1) ->start()
2) ->add_interface()
3) ->sta_notify() [which iwlwifi doesn't use]
4) ->set_key()
5) ->bss_info_changed()
and some more. Now, because iwlwifi ignores step 3, in step 4 it will
complain "station not found" when mac80211 wants to add the pairwise key
for the AP. Reordering 4 and 5 fixes that because iwlwifi adds the
station in bss_info_changed and then the key upload can be successful.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-10 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 0:55 [PATCH] mac80211: re-upload keys only after telling driver about association Johannes Berg
2009-04-09 16:26 ` reinette chatre
2009-04-10 7:29 ` Johannes Berg [this message]
2009-04-10 16:05 ` reinette chatre
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=1239348556.17031.14.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=bcopeland@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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