diff options
author | Johannes Berg <johannes.berg@intel.com> | 2013-12-18 08:43:33 (GMT) |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2013-12-19 12:33:33 (GMT) |
commit | 34a3740d6b392896b71e36cd5cd68837a8f94a5c (patch) | |
tree | 128f9a3e35af1e7fc768b55fc7173cac9e1a3b08 /drivers | |
parent | 6924d0138acdf5026ee4463134d98e139fe025a2 (diff) | |
download | linux-34a3740d6b392896b71e36cd5cd68837a8f94a5c.tar.xz |
mac80211: fix iflist_mtx/mtx locking in radar detection
The scan code creates an iflist_mtx -> mtx locking dependency,
and a few other places, notably radar detection, were creating
the opposite dependency, causing lockdep to complain. As scan
and radar detection are mutually exclusive, the deadlock can't
really happen in practice, but it's still bad form.
A similar issue exists in the monitor mode code, but this is
only used by channel-context drivers right now and those have
to have hardware scan, so that also can't happen.
Still, fix these issues by making some of the channel context
code require the mtx to be held rather than acquiring it, thus
allowing the monitor/radar callers to keep the iflist_mtx->mtx
lock ordering.
While at it, also fix access to the local->scanning variable
in the radar code, and document that radar_detect_enabled is
now properly protected by the mtx.
All this would now introduce an ABBA deadlock between the DFS
work cancelling and local->mtx, so change the locking there a
bit to not need to use cancel_delayed_work_sync() but be able
to just use cancel_delayed_work(). The work is also safely
stopped/removed when the interface is stopped, so no extra
changes are needed.
Reported-by: Kalle Valo <kvalo@qca.qualcomm.com>
Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions