From: Brian Norris <briannorris@chromium.org> To: Kalle Valo <kvalo@codeaurora.org> Cc: cjhuang@codeaurora.org, Arend van Spriel <arend.vanspriel@broadcom.com>, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Subject: Re: [PATCH 2/2] ath10k: support MAC address randomization in scan Date: Mon, 16 Apr 2018 17:28:56 -0700 [thread overview] Message-ID: <20180417002854.GA186697@rodete-desktop-imager.corp.google.com> (raw) In-Reply-To: <8736zvqtcw.fsf@kamboji.qca.qualcomm.com> Hi, On Mon, Apr 16, 2018 at 02:32:47PM +0300, Kalle Valo wrote: > cjhuang@codeaurora.org writes: > > On 2018-04-14 05:13, Arend van Spriel wrote: > >> On 4/13/2018 1:28 PM, Kalle Valo wrote: > >>> cjhuang@codeaurora.org writes: > >>> > >>>>>> + if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT, ar->wmi.svc_map)) { > >>>>>> + ret = ath10k_wmi_scan_prob_req_oui(ar, ar->mac_addr); > >>>>>> + if (ret) { > >>>>>> + ath10k_err(ar, "failed to set prob req oui: %i\n", ret); > >>>>>> + goto err_dfs_detector_exit; > >>>>>> + } > >>>>>> + > >>>>>> + ar->hw->wiphy->features |= > >>>>>> + NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR; > >>>>> > >>>>> Do you support NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR too? > >>>> > >>>> I'll add this flag too. > >>> > >>> Are you going to send v2 or what's the plan? > >> > >> Maybe a stupid question, but does ath10k support scheduled scan? Not a stupid question. Sorry for not asking that first. > AFAICS ath10k does not support it (sched_scan_start() op). Right, that seems to be the case. > > The reason is AVL test case needs this flag to enable random mac > > address scan. Maybe Brian Can explain why this flag is necessary. I never actually claimed you *needed* this flag; I just wondered how you claimed to pass our test when you did not support this flag, since our network manager currently checks for both NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR and NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR before enabling MAC randomization in scans. But that's no matter to worry about here. > If ath10k does not support scheduled scan what's the point? Shouldn't > the test case then be it fixed instead of making hacks in ath10k? Indeed. We're trying to work that out right now. It looks like the status quo for looking for SCHED_SCAN support is to check if NL80211_CMD_START_SCHED_SCAN shows up in the command support list. (IOW, that's what wpa_supplicant does.) We'll probably need to imitate that. Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <briannorris@chromium.org> To: Kalle Valo <kvalo@codeaurora.org> Cc: Arend van Spriel <arend.vanspriel@broadcom.com>, cjhuang@codeaurora.org, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Subject: Re: [PATCH 2/2] ath10k: support MAC address randomization in scan Date: Mon, 16 Apr 2018 17:28:56 -0700 [thread overview] Message-ID: <20180417002854.GA186697@rodete-desktop-imager.corp.google.com> (raw) In-Reply-To: <8736zvqtcw.fsf@kamboji.qca.qualcomm.com> Hi, On Mon, Apr 16, 2018 at 02:32:47PM +0300, Kalle Valo wrote: > cjhuang@codeaurora.org writes: > > On 2018-04-14 05:13, Arend van Spriel wrote: > >> On 4/13/2018 1:28 PM, Kalle Valo wrote: > >>> cjhuang@codeaurora.org writes: > >>> > >>>>>> + if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT, ar->wmi.svc_map)) { > >>>>>> + ret = ath10k_wmi_scan_prob_req_oui(ar, ar->mac_addr); > >>>>>> + if (ret) { > >>>>>> + ath10k_err(ar, "failed to set prob req oui: %i\n", ret); > >>>>>> + goto err_dfs_detector_exit; > >>>>>> + } > >>>>>> + > >>>>>> + ar->hw->wiphy->features |= > >>>>>> + NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR; > >>>>> > >>>>> Do you support NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR too? > >>>> > >>>> I'll add this flag too. > >>> > >>> Are you going to send v2 or what's the plan? > >> > >> Maybe a stupid question, but does ath10k support scheduled scan? Not a stupid question. Sorry for not asking that first. > AFAICS ath10k does not support it (sched_scan_start() op). Right, that seems to be the case. > > The reason is AVL test case needs this flag to enable random mac > > address scan. Maybe Brian Can explain why this flag is necessary. I never actually claimed you *needed* this flag; I just wondered how you claimed to pass our test when you did not support this flag, since our network manager currently checks for both NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR and NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR before enabling MAC randomization in scans. But that's no matter to worry about here. > If ath10k does not support scheduled scan what's the point? Shouldn't > the test case then be it fixed instead of making hacks in ath10k? Indeed. We're trying to work that out right now. It looks like the status quo for looking for SCHED_SCAN support is to check if NL80211_CMD_START_SCHED_SCAN shows up in the command support list. (IOW, that's what wpa_supplicant does.) We'll probably need to imitate that. Brian _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-17 0:28 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-30 3:13 [PATCH 0/2] ath10k: support MAC address randomization in scan Carl Huang 2018-03-30 3:13 ` Carl Huang 2018-03-30 3:13 ` [PATCH 1/2] ath10k: Add WMI_SERVICE_AVAILABLE_EVENT support Carl Huang 2018-03-30 3:13 ` Carl Huang 2018-04-16 13:40 ` [1/2] " Kalle Valo 2018-04-16 13:40 ` Kalle Valo 2018-04-24 5:46 ` Kalle Valo 2018-04-24 5:46 ` Kalle Valo 2018-03-30 3:14 ` [PATCH 2/2] ath10k: support MAC address randomization in scan Carl Huang 2018-03-30 3:14 ` Carl Huang 2018-04-12 20:59 ` Brian Norris 2018-04-12 20:59 ` Brian Norris 2018-04-13 6:53 ` cjhuang 2018-04-13 6:53 ` cjhuang 2018-04-13 11:28 ` Kalle Valo 2018-04-13 11:28 ` Kalle Valo 2018-04-13 21:13 ` Arend van Spriel 2018-04-13 21:13 ` Arend van Spriel 2018-04-16 5:16 ` cjhuang 2018-04-16 5:16 ` cjhuang 2018-04-16 11:32 ` Kalle Valo 2018-04-16 11:32 ` Kalle Valo 2018-04-17 0:28 ` Brian Norris [this message] 2018-04-17 0:28 ` Brian Norris 2018-04-17 8:22 ` Arend van Spriel 2018-04-17 8:22 ` Arend van Spriel 2018-04-17 16:07 ` Brian Norris 2018-04-17 16:07 ` Brian Norris 2018-04-17 21:49 ` Arend van Spriel 2018-04-17 21:49 ` Arend van Spriel 2018-04-17 22:26 ` Brian Norris 2018-04-17 22:26 ` Brian Norris 2018-04-18 2:35 ` Dan Williams 2018-04-18 2:35 ` Dan Williams 2018-04-18 8:29 ` Arend van Spriel 2018-04-18 8:29 ` Arend van Spriel 2018-04-18 9:58 ` Johannes Berg 2018-04-18 9:58 ` Johannes Berg 2018-04-16 5:17 ` cjhuang 2018-04-16 5:17 ` cjhuang 2018-04-16 13:42 ` [2/2] " Kalle Valo 2018-04-16 13:42 ` Kalle Valo [not found] ` <20180416134238.B16596076A@smtp.codeaurora.org> 2018-04-17 7:29 ` cjhuang 2018-04-17 7:29 ` cjhuang 2018-04-20 10:30 ` Kalle Valo 2018-04-20 10:30 ` Kalle Valo
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=20180417002854.GA186697@rodete-desktop-imager.corp.google.com \ --to=briannorris@chromium.org \ --cc=arend.vanspriel@broadcom.com \ --cc=ath10k@lists.infradead.org \ --cc=cjhuang@codeaurora.org \ --cc=kvalo@codeaurora.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: linkBe 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.