From: Johannes Berg <johannes@sipsolutions.net>
To: "Kanchanapally, Vidyullatha" <vkanchan@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, jouni@qca.qualcomm.com,
usdutt@qti.qualcomm.com, amarnath@qca.qualcomm.com
Subject: Re: [PATCH 1/3] cfg80211: Add option to report the bss entry in connect result
Date: Thu, 14 Apr 2016 11:01:47 +0200 [thread overview]
Message-ID: <1460624507.2358.9.camel@sipsolutions.net> (raw)
In-Reply-To: <1460367961-11254-1-git-send-email-vkanchan@qti.qualcomm.com>
On Mon, 2016-04-11 at 15:16 +0530, Kanchanapally, Vidyullatha wrote:
> From: "Kanchanapally, Vidyullatha" <vkanchan@qti.qualcomm.com>
>
> Since cfg80211 maintains separate BSS table entries for APs if the
> same
> BSSID, SSID pair is seen on multiple channels, it is possible that it
> can map the current_bss to a BSS entry on the wrong channel. This
> current_bss will not get flushed unless disconnected and cfg80211
> reports a wrong channel as the associated channel.
>
> Fix this by introducing a new cfg80211_connect_bss() function which
> is
> similar to cfg80211_connect_result(), but it includes an additional
> parameter: the bss the STA is connected to. This allows drivers to
> provide the exact bss entry that matches the BSS to which the
> connection
> was completed.
Applied.
I'm surprised you're so worried about this test scenario (we've
discussed this multiple times before), but I can't really argue with
passing the BSS pointer either :)
johannes
prev parent reply other threads:[~2016-04-14 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 9:46 [PATCH 1/3] cfg80211: Add option to report the bss entry in connect result Kanchanapally, Vidyullatha
2016-04-12 8:52 ` Arend van Spriel
2016-04-12 9:34 ` Kanchanapally, Vidyullatha
2016-04-14 9:01 ` Johannes Berg [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=1460624507.2358.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amarnath@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=usdutt@qti.qualcomm.com \
--cc=vkanchan@qti.qualcomm.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 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.