linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	David Spinadel <david.spinadel@intel.com>
Subject: Re: [PATCH] mac80211: stop scan before connection
Date: Wed, 18 Mar 2015 10:46:21 +0100	[thread overview]
Message-ID: <1426671981.3001.12.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEd7cQwKm_yLztzeTB0S_-uEp4FwzDUV1O8cG6mNtkiY_A@mail.gmail.com> (sfid-20150318_103655_610322_AA890276)

On Wed, 2015-03-18 at 11:36 +0200, Eliad Peller wrote:
> On Tue, Mar 17, 2015 at 7:58 PM, Emmanuel Grumbach
> <emmanuel.grumbach@intel.com> wrote:
> > From: David Spinadel <david.spinadel@intel.com>
> >
> > Stop scan before authentication or association to make sure
> > that nothing interferes with connection flow.
> >
> this makes sense
> 
> > Currently mac80211 defers RX auth and assoc packets (among other ones)
> > until after the scan is complete, so auth during scan is likely to fail
> > if scan took too much time.
> >
> but i don't think deferring the frame handling makes sense in case of
> hw_scan (there was a similar case with BA request handling).
> i should have such (one-liner) patch pending somewhere...

We did consider that, but ultimately I think it's not desirable.

The aggregation case is different, but during auth/assoc the relevant
frames cannot be buffered by the AP. So unless you have a hardware
mechanism that makes the device not continue the scan for say 30-50ms
after the auth/assoc req frame went out, the connection process will be
very unreliable.

So in a sense you could say deferring the handling doesn't make sense,
but I'd still argue you shouldn't start this process while you're in the
middle of scanning, hence this patch.

We may have to do more exclusions (e.g. don't start a scan while
authenticating or associating) here though, and ultimately not
*processing* the frames will be irrelevant as they shouldn't be coming
in anyway.

johannes


  reply	other threads:[~2015-03-18  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 17:58 [PATCH] mac80211: stop scan before connection Emmanuel Grumbach
2015-03-18  9:36 ` Eliad Peller
2015-03-18  9:46   ` Johannes Berg [this message]
2015-03-18 10:11     ` Eliad Peller
2015-03-18 19:22       ` Johannes Berg
2015-03-30  8:19 ` 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=1426671981.3001.12.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=david.spinadel@intel.com \
    --cc=eliad@wizery.com \
    --cc=emmanuel.grumbach@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).