diff options
author | Johannes Berg <johannes.berg@intel.com> | 2014-01-22 10:14:19 +0100 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2014-02-06 09:55:19 +0100 |
commit | f9d15d162b3acf28f85b3ac05c4883e5ed588d28 (patch) | |
tree | 1c78c9fd0d81302190738d2778db000f9506e4fa /firmware | |
parent | cfg80211: fix scan done race (diff) | |
download | linux-f9d15d162b3acf28f85b3ac05c4883e5ed588d28.tar.xz linux-f9d15d162b3acf28f85b3ac05c4883e5ed588d28.zip |
cfg80211: send scan results from work queue
Due to the previous commit, when a scan finishes, it is in theory
possible to hit the following sequence:
1. interface starts being removed
2. scan is cancelled by driver and cfg80211 is notified
3. scan done work is scheduled
4. interface is removed completely, rdev->scan_req is freed,
event sent to userspace but scan done work remains pending
5. new scan is requested on another virtual interface
6. scan done work runs, freeing the still-running scan
To fix this situation, hang on to the scan done message and block
new scans while that is the case, and only send the message from
the work function, regardless of whether the scan_req is already
freed from interface removal. This makes step 5 above impossible
and changes step 6 to be
5. scan done work runs, sending the scan done message
As this can't work for wext, so we send the message immediately,
but this shouldn't be an issue since we still return -EBUSY.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions