Due to userspace assumptions, the sched_scan_stop operation must be synchronous, i.e. once it returns a new scheduled scan must be able to start immediately. Document this in the API.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -303,8 +303,9 @@ · 302 unmodified lines | ||
| 303 | 303 | * passed, all channels allowed for the current regulatory domain |
| 304 | 304 | * are used. Extra IEs can also be passed from the userspace by |
| 305 | 305 | * using the %NL80211_ATTR_IE attribute. |
| 306 | − * @NL80211_CMD_STOP_SCHED_SCAN: stop a scheduled scan. Returns -ENOENT | |
| 307 | − * if scheduled scan is not running. | |
| 306 | + * @NL80211_CMD_STOP_SCHED_SCAN: stop a scheduled scan. Returns -ENOENT if | |
| 307 | + * scheduled scan is not running. The caller may assume that as soon | |
| 308 | + * as the call returns, it is safe to start a new scheduled scan again. | |
| 308 | 309 | * @NL80211_CMD_SCHED_SCAN_RESULTS: indicates that there are scheduled scan |
| 309 | 310 | * results available. |
| 310 | 311 | * @NL80211_CMD_SCHED_SCAN_STOPPED: indicates that the scheduled scan has |