Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Johannes Berg'" <johannes@sipsolutions.net>,
	"'John W. Linville'" <linville@tuxdriver.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: SIOCGIWSCAN-race
Date: Tue, 24 Feb 2009 06:55:39 +0100	[thread overview]
Message-ID: <385AA299C8A542839E1BCA8302900524@gotws1589> (raw)
In-Reply-To: <1235440092.4455.40.camel@johannes.local>

> On Mon, 2009-02-23 at 16:11 -0500, John W. Linville wrote:
> > On Sat, Feb 21, 2009 at 08:33:06AM +0100, Lars Ericsson wrote:
> > > Hi Johannes,
> > > 
> > > I have discovered and patched a race in the scanning function since a
couple
> > > of releases.
> > > To day I checked the current Linux git and the problem is still there.
> > > 
> > > The problem is the sequence of events when the scan result is reported
back.
> > > The wireless_send_event(dev, SIOCGIWSCAN, &wrqu, NULL); 
> > > is called before ieee80211_hw_config(local);
> > > 
> > > ieee80211_hw_config(local) will trig the wpa_supplicant to select an
AP. 
> > > That may happen before the ieee80211_hw_config() is executed since the
> > > wpa_supplicant
> > > generated actions is executed by an other thread (wpa_supplicant).
> > > 
> > > The result is that:
> > > - wpa_supplicant setup for an association to an ap using correct
channel.
> > > - ieee80211_hw_config() reset the channel to the value before the SCAN
started.
> > > - the association request will be sent out using the wrong channel.
> > > 
> > > 
> > > Attached you will find the patch for 2.6.27. 
> > > It is not a perfect patch since the code is duplicated but it works :)
> > 
> > Looks like the patch would need to be reworked -- the code in 2.6.29
> > and later is different.  
> 
> and the new code with cfg80211 is even more different ;)
> 

OK, I have not moved in to the 'cfg80211' world, yet.
Johannes; do you create the patch for this ?
 
> > Also, any reason we can't just move the
> > wireless_send_event() down to done:?
> 
> seems fine

Perfect, is it to late for 2.6.29 ?

Lars

> > Still, this doesn't feel quite right.  Shouldn't we be able to queue
> > the userland-driven channel change until after the scan completes?
> 
> ?
> we do that, well, we set it here:
>         local->sw_scanning = false;
>         ieee80211_hw_config(local, IEEE80211_CONF_CHANGE_CHANNEL);
> 
> but we claim to be on the user requested channel at all times, so that
> should be ok
> 
> johannes
> 
> > John
> > 
> > diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
> > index f5c7c33..8c13a91 100644
> > --- a/net/mac80211/scan.c
> > +++ b/net/mac80211/scan.c
> > @@ -437,15 +437,6 @@ void ieee80211_scan_completed(struct 
> ieee80211_hw *hw)
> >  	local->last_scan_completed = jiffies;
> >  	memset(&wrqu, 0, sizeof(wrqu));
> >  
> > -	/*
> > -	 * local->scan_sdata could have been NULLed by the interface
> > -	 * down code in case we were scanning on an interface that is
> > -	 * being taken down.
> > -	 */
> > -	sdata = local->scan_sdata;
> > -	if (sdata)
> > -		wireless_send_event(sdata->dev, SIOCGIWSCAN, 
> &wrqu, NULL);
> > -
> >  	if (local->hw_scanning) {
> >  		local->hw_scanning = false;
> >  		/*
> > @@ -486,6 +477,15 @@ void ieee80211_scan_completed(struct 
> ieee80211_hw *hw)
> >  	rcu_read_unlock();
> >  
> >   done:
> > +	/*
> > +	 * local->scan_sdata could have been NULLed by the interface
> > +	 * down code in case we were scanning on an interface that is
> > +	 * being taken down.
> > +	 */
> > +	sdata = local->scan_sdata;
> > +	if (sdata)
> > +		wireless_send_event(sdata->dev, SIOCGIWSCAN, 
> &wrqu, NULL);
> > +
> >  	ieee80211_mlme_notify_scan_completed(local);
> >  	ieee80211_mesh_notify_scan_completed(local);
> >  }
> > 
> 


      reply	other threads:[~2009-02-24  7:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21  7:33 SIOCGIWSCAN-race Lars Ericsson
2009-02-23 21:11 ` SIOCGIWSCAN-race John W. Linville
2009-02-24  1:48   ` SIOCGIWSCAN-race Johannes Berg
2009-02-24  5:55     ` Lars Ericsson [this message]

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=385AA299C8A542839E1BCA8302900524@gotws1589 \
    --to=lars_ericsson@telia.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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