From: Antonio Quartulli <antonio@meshcoding.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, stefan.pietsch@lsexperts.de
Subject: Re: [PATCH 2/2] cfg80211: ignore invalid BSSIDs when looking for BSSes
Date: Thu, 10 Apr 2014 10:25:53 +0200 [thread overview]
Message-ID: <53465591.7000404@meshcoding.com> (raw)
In-Reply-To: <1397116783.4757.4.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On 10/04/14 09:59, Johannes Berg wrote:
> On Thu, 2014-04-10 at 09:00 +0200, Antonio Quartulli wrote:
>> On 09/04/14 22:39, Johannes Berg wrote:
>>> diff --git a/net/wireless/scan.c b/net/wireless/scan.c
>>> index 7d09a712cb1f..746c56ebd66c 100644
>>> --- a/net/wireless/scan.c
>>> +++ b/net/wireless/scan.c
>>> @@ -540,6 +540,8 @@ struct cfg80211_bss *cfg80211_get_bss(struct wiphy *wiphy,
>>> continue;
>>> if (channel && bss->pub.channel != channel)
>>> continue;
>>> + if (!is_valid_ether_addr(bss->pub.bssid))
>>> + continue;
>>
>> Wouldn't it be better to prevent such entry to end up in the bss list at
>> all? (i.e. filtering during the scan?)
>
> I thought about that, but I'm not so sure.
>
> On the one hand, that would make sense since it's unusable, on the other
> hand it could cause confusion if you don't see some other network that
> you expect to show up ...
I agree here.
Showing the network is reasonable because the user expects to see what's
around. Imagine a user that scans just to see which channel is less
crowded...
>
> And then again, if you can click the network in the UI and then it won't
> connect to it, that also causes confusion. I'm not sure what the best
> way is ...
>
True. But here it's up to the UI to check the MAC and tell the user that
this is an invalid BSSID, no?
In the end I drop my original objection :)
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2014-04-10 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 20:39 [PATCH 1/2] cfg80211: reject invalid IBSS BSSIDs in wext compat code Johannes Berg
2014-04-09 20:39 ` [PATCH 2/2] cfg80211: ignore invalid BSSIDs when looking for BSSes Johannes Berg
2014-04-10 7:00 ` Antonio Quartulli
2014-04-10 7:59 ` Johannes Berg
2014-04-10 8:25 ` Antonio Quartulli [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=53465591.7000404@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=stefan.pietsch@lsexperts.de \
/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.