From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>,
Antonio Quartulli <antonio@open-mesh.com>,
Arend van Spriel <arend@broadcom.com>,
Bing Zhao <bzhao@marvell.com>,
"Jussi Kivilinna" <jussi.kivilinna@iki.fi>,
<libertas-dev@lists.infradead.org>
Subject: Re: [PATCHv2] cfg80211: fix channel configuration in IBSS join
Date: Wed, 29 Jan 2014 17:12:38 +0200 [thread overview]
Message-ID: <87eh3q255l.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1391002505-3771-1-git-send-email-antonio@meshcoding.com> (Antonio Quartulli's message of "Wed, 29 Jan 2014 14:35:05 +0100")
Antonio Quartulli <antonio@meshcoding.com> writes:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> When receiving an IBSS_JOINED event select the BSS object
> based on the {bssid, channel} couple rather than the bssid
> only.
> With the current approach if another cell having the same
> BSSID (but using a different channel) exists then cfg80211
> picks up the wrong BSS object.
> The result is a mismatching channel configuration between
> cfg80211 and the driver, that can lead to any sort of
> problem.
>
> The issue can be triggered by having an IBSS sitting on
> given channel and then asking the driver to create a new
> cell using the same BSSID but with a different frequency.
> By passing the channel to cfg80211_get_bss() we can solve
> this ambiguity and retrieve/create the correct BSS object.
> All the users of cfg80211_ibss_joined() have been changed
> accordingly.
>
> Moreover WARN when cfg80211_ibss_joined() gets a NULL
> channel as argument and remove a bogus call of the same
> function in ath6kl (it does not make sense to call
> cfg80211_ibss_joined() with a zero BSSID on ibss-leave).
>
> Cc: Kalle Valo <kvalo@qca.qualcomm.com>
> Cc: Arend van Spriel <arend@broadcom.com>
> Cc: Bing Zhao <bzhao@marvell.com>
> Cc: Jussi Kivilinna <jussi.kivilinna@iki.fi>
> Cc: libertas-dev@lists.infradead.org
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
For the ath6kl part:
Acked-by: Kalle Valo <kvalo@qca.qualcomm.com>
--
Kalle Valo
prev parent reply other threads:[~2014-01-29 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 13:35 [PATCHv2] cfg80211: fix channel configuration in IBSS join Antonio Quartulli
2014-01-29 15:12 ` Kalle Valo [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=87eh3q255l.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=antonio@meshcoding.com \
--cc=antonio@open-mesh.com \
--cc=arend@broadcom.com \
--cc=bzhao@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=jussi.kivilinna@iki.fi \
--cc=libertas-dev@lists.infradead.org \
--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.