From: "Cédric Debarge - ACKSYS" <cedric.debarge@acksys.fr>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: missing RX_FLAG_DECRIPTED in ieee80211_rx_status after first reassociation in 802.11R
Date: Thu, 10 Jan 2013 11:18:40 +0100 [thread overview]
Message-ID: <018801cdef1b$dca15b10$95e41130$@acksys.fr> (raw)
In-Reply-To: <1357734417.9757.6.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]
Hi Johannes,
Thank you for you answer.
Sorry for the answer delay, I wasn't familiar with the kernel tracing features.
I attached the trace file since it is quite long (about 1400 lines).
Here are some pointers :
Original AP = 90:A4:DE:AA:42:94, channel : 132, ssid : acksyscdtest
Second AP = 90:A4:DE:AA:41:ED, channel : 132, ssid : acksyscdtest
When wpa_supplicant is launched, it associates directly with 90:A4:DE:AA:42:94.
The roaming order is given by the wpa_cli roam command (roam 90:A4:DE:AA:41:ED). You can find it at line 1042 of the traces.
I used the -T option of wpa_supplicant.
In order to get cfg80211 traces I had to switch to compat wireless version 2012-12-06 (previous was 2012-09-07). Nevertheless, the behavior seems to remain the same (same exit in ieee80211_key_enable_hw_accel at the first roam).
Just let me know if you need more information.
Best regards,
Cédric DEBARGE
-----Message d'origine-----
De : Johannes Berg [mailto:johannes@sipsolutions.net]
Envoyé : mercredi 9 janvier 2013 13:27
À : Cedric Debarge
Cc : linux-wireless@vger.kernel.org
Objet : Re: missing RX_FLAG_DECRIPTED in ieee80211_rx_status after first reassociation in 802.11R
On Tue, 2013-01-08 at 12:11 +0100, Cedric Debarge wrote:
> Hi all,
>
> I dug a little more on this problem and I found that hardware encryption is disabled after the first roam because ieee80211_key_enable_hw_accel fails on the following test :
> if (sta && !sta->uploaded)
> goto out_unsupported;
>
> After the first roam, sta->uploaded is tested before sta_info_move_state sets it to true.
>
> At the first association/authentication :
> 1) sta_info_move_state sets sta->uploaded to true
> 2) ieee80211_key_enable_hw_accel test it and find it true -->
> hardware decoding
>
> When the station changes from an AP to another :
> 1) ieee80211_key_enable_hw_accel test it and find it false --> software decoding
> 2) sta_info_move_state sets sta->uploaded to true
I cannot reproduce this. Could you obtain tracing information ("trace-cmd record -e cfg80211") on an affected system?
Also a wpa_supplicant debug log would be helpful. Or better yet, use a new supplicant with the "-T" parameter -- this will make its debug information go into the cfg80211 tracing that you record as per above.
johannes
[-- Attachment #2: trace.dat --]
[-- Type: application/octet-stream, Size: 684913 bytes --]
next prev parent reply other threads:[~2013-01-10 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 11:11 missing RX_FLAG_DECRIPTED in ieee80211_rx_status after first reassociation in 802.11R Cedric Debarge
2013-01-09 12:26 ` Johannes Berg
2013-01-10 10:18 ` Cédric Debarge - ACKSYS [this message]
2013-01-10 12:30 ` Johannes Berg
2013-01-10 13:28 ` Cédric Debarge - ACKSYS
-- strict thread matches above, loose matches on Subject: below --
2012-12-26 10:09 Cedric Debarge
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='018801cdef1b$dca15b10$95e41130$@acksys.fr' \
--to=cedric.debarge@acksys.fr \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.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 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.