From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC V2 1/5] nl80211: allow multiple active scheduled scan requests
Date: Tue, 24 Jan 2017 10:40:15 +0100 [thread overview]
Message-ID: <1485250815.7244.8.camel@sipsolutions.net> (raw)
In-Reply-To: <1484566941-27000-2-git-send-email-arend.vanspriel@broadcom.com>
> + * @max_sched_scan_reqs: maximum number of scheduled scan requests
> that
> + * the device can run concurrently.
Perhaps we should get rid of WIPHY_FLAG_SUPPORTS_SCHED_SCAN and just
set this to 1 for such devices? Otherwise we have two different
requirements, and we need to track that 0 is an invalid value here if
WIPHY_FLAG_SUPPORTS_SCHED_SCAN is set, or something like that?
> + * @NL80211_ATTR_SCHED_SCAN_MAX_REQS: indicates maximum number of
> scheduled
> + * scan request that may be active for the device (u8).
I'd make that a u32 - not that I believe we'll ever want to change this
in the future, but there's simply no value in making it a u8 since it
uses the same amount of space in a netlink message.
> + list_for_each_entry_safe(pos, tmp, &rdev-
> >sched_scan_req_list, list) {
> + cfg80211_stop_sched_scan_req(rdev, pos, false);
> + }
nit: don't really need braces here.
> + if ((wiphy->flags & WIPHY_FLAG_SUPPORTS_SCHED_SCAN) &&
> + !wiphy->max_sched_scan_reqs)
> + wiphy->max_sched_scan_reqs = 1;
Yeah, this. Why bother?
(should even be simple to come up with an spatch to change all the
drivers, but there are only five anyway)
> + nla_put_u8(msg,
> NL80211_ATTR_SCHED_SCAN_MAX_REQS,
> + rdev->wiphy.max_sched_scan_reqs) ||
> nla_put_u8(msg,
> NL80211_ATTR_MAX_NUM_SCHED_SCAN_SSIDS,
> rdev->wiphy.max_sched_scan_ssids) ||
This might break older userspace - you'll have to put it in a later
portion of the code.
I'm also a bit surprised the attributes aren't actually optional for
when sched scan isn't supported, I'd make the new one optional and I
guess we can fix the others later too, if desired.
> + bool want_multi;
That's bool
> + want_multi = !!info->attrs[NL80211_ATTR_SCHED_SCAN_MULTI];
so you don't really need the !! as it's implied by the rules for bool
:)
> + /* leave request id zero for legacy request
> + * or if driver does not support multi-scheduled scan
> + */
> + if (want_multi && rdev->wiphy.max_sched_scan_reqs > 1) {
Why do the >1 check here? It probably doesn't really make a difference
since only one can be running at a time, but it might be nicer - at
least for debug in userspace - to have a real value for all multi
scans?
> + while (!sched_scan_req->reqid)
Pretty sure we won't run over the u64 ... but I guess it doesn't matter
much :)
I don't see you sending the reqid/cookie back to userspace here though,
that's missing?
> static int nl80211_stop_sched_scan(struct sk_buff *skb,
> struct genl_info *info)
> {
> + struct cfg80211_sched_scan_request *req;
> struct cfg80211_registered_device *rdev = info->user_ptr[0];
> + u64 cookie;
>
> if (!(rdev->wiphy.flags & WIPHY_FLAG_SUPPORTS_SCHED_SCAN) ||
> !rdev->ops->sched_scan_stop)
> return -EOPNOTSUPP;
>
> - return __cfg80211_stop_sched_scan(rdev, false);
> + if (info->attrs[NL80211_ATTR_COOKIE]) {
> + cookie = nla_get_u64(info-
> >attrs[NL80211_ATTR_COOKIE]);
> + return __cfg80211_stop_sched_scan(rdev, cookie,
> false);
> + } else {
> + req = list_first_or_null_rcu(&rdev-
> >sched_scan_req_list,
> + struct
> cfg80211_sched_scan_request,
> + list);
> + if (!req || req->reqid ||
> + (req->owner_nlportid &&
> + req->owner_nlportid != info->snd_portid))
> + return -ENOENT;
Shouldn't this also check that it's non-multi?
> +void cfg80211_add_sched_scan_req(struct cfg80211_registered_device
> *rdev,
> + struct cfg80211_sched_scan_request
> *req)
> +{
> + list_add_rcu(&req->list, &rdev->sched_scan_req_list);
> +}
> +
> +static void cfg80211_del_sched_scan_req(struct
> cfg80211_registered_device *rdev,
> + struct
> cfg80211_sched_scan_request *req)
> +{
> + list_del_rcu(&req->list);
> + kfree_rcu(req, rcu_head);
> +}
Some locking assertions in these would be good, I think.
> +static struct cfg80211_sched_scan_request *
> +cfg80211_find_sched_scan_req(struct cfg80211_registered_device
> *rdev, u64 reqid)
> +{
> + struct cfg80211_sched_scan_request *pos;
> +
> + list_for_each_entry(pos, &rdev->sched_scan_req_list, list) {
> + if (pos->reqid == reqid)
> + return pos;
> + }
> + return ERR_PTR(-ENOENT);
> +}
Here too, I guess, since you don't actually use RCU.
johannes
next prev parent reply other threads:[~2017-01-24 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 11:42 [RFC V2 0/5] cfg80211: support multiple scheduled scans Arend van Spriel
2017-01-16 11:42 ` [RFC V2 1/5] nl80211: allow multiple active scheduled scan requests Arend van Spriel
2017-01-24 9:40 ` Johannes Berg [this message]
2017-02-14 12:35 ` Arend Van Spriel
2017-02-14 12:51 ` Johannes Berg
2017-02-14 13:07 ` Arend Van Spriel
2017-02-14 13:12 ` Johannes Berg
2017-02-14 20:09 ` Arend Van Spriel
2017-02-14 20:11 ` Johannes Berg
2017-02-15 10:55 ` Arend Van Spriel
2017-02-15 10:59 ` Johannes Berg
2017-02-14 13:33 ` Arend Van Spriel
2017-02-14 13:34 ` Johannes Berg
2017-01-16 11:42 ` [RFC V2 2/5] nl80211: include request id in scheduled scan event messages Arend van Spriel
2017-01-16 11:42 ` [RFC V2 3/5] cfg80211: add request id parameter to .sched_scan_stop() signature Arend van Spriel
2017-01-16 11:42 ` [RFC V2 4/5] cfg80211: add request id to cfg80211_sched_scan_results() api Arend van Spriel
2017-01-16 11:42 ` [RFC V2 5/5] cfg80211: add request id in cfg80211_sched_scan_stopped{,_rtnl}() api Arend van Spriel
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=1485250815.7244.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--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).