From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>,
<brcm80211-dev-list@broadcom.com>,
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: [PATCH RESEND mac80211] cfg80211: fix channel configuration in IBSS join
Date: Tue, 28 Jan 2014 15:01:47 +0200 [thread overview]
Message-ID: <87wqhkgszo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1390913540-2127-1-git-send-email-antonio@meshcoding.com> (Antonio Quartulli's message of "Tue, 28 Jan 2014 13:52:20 +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.
>
> 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@meshcoding.com>
> ---
>
> - Patch is getting resent because I did not CC'd the linux-wireless mailing list in
> my previous attempt. :)
Oh, I missed that. Anyway, in previous version I commented about
documenting NULL usage. What do you think about that?
--
Kalle Valo
next prev parent reply other threads:[~2014-01-28 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 12:52 [PATCH RESEND mac80211] cfg80211: fix channel configuration in IBSS join Antonio Quartulli
2014-01-28 13:01 ` Kalle Valo [this message]
2014-01-28 13:31 ` Antonio Quartulli
2014-01-28 13:36 ` Johannes Berg
2014-01-28 13:36 ` Antonio Quartulli
2014-01-29 12:10 ` Johannes Berg
2014-01-29 12:12 ` 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=87wqhkgszo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=antonio@meshcoding.com \
--cc=antonio@open-mesh.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@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 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).