On Tue, 2016-11-22 at 14:12 +0100, Arend Van Spriel wrote: > On 22-11-2016 11:22, Arend van Spriel wrote: > > When user-space does not provide scheduled scan plans, ie. uses the > > old scheduled scan API containing NL80211_ATTR_SCHED_SCAN_INTERVAL. > > The interval value passed by user-space is validated against > > struct wiphy::max_sched_scan_plan_interval and if it is exceeding > > it the interval is set to struct wiphy::max_sched_scan_plan_interval. > > However, when the driver does not set this limit the interval the > > interval in the request will always be zero. Hence add a check to > > see whether the driver set struct wiphy::max_sched_scan_plan_interval. > > > > For the new API, ie. for scheduled scan plans, the interval validation > > has been simalarly adjusted to assure the limit is non-zero. > > Actually turns out that max_sched_scan_plan_interval is always set in > wiphy_new_nm() which is used by all drivers so please drop this patch. Right, I mixed mac80211 into the picture and got confused. -- Luca.
