Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Cedric Debarge <cedric.debarge@acksys.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: missing RX_FLAG_DECRIPTED in ieee80211_rx_status after first reassociation in 802.11R
Date: Wed, 09 Jan 2013 13:26:57 +0100	[thread overview]
Message-ID: <1357734417.9757.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <773DB8A82AB6A046AE0195C68612A319014B7055@sbs2003.acksys.local> (sfid-20130108_123142_580099_93DD6C6E)

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


  reply	other threads:[~2013-01-09 12:26 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 [this message]
2013-01-10 10:18   ` Cédric Debarge - ACKSYS
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=1357734417.9757.6.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=cedric.debarge@acksys.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox