diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2010-07-29 11:37:41 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2010-07-29 12:55:00 -0400 |
| commit | d28232b461b8d54b09e59325dbac8b0913ce2049 (patch) | |
| tree | 86b9fbd210d63f60056f9d8fb6b4dc5ded6a40d2 /net/mac80211/work.c | |
| parent | 16345910d927556878a82621ebb9a7bcad13e8d8 (diff) | |
| download | kernel_samsung_smdk4412-d28232b461b8d54b09e59325dbac8b0913ce2049.zip kernel_samsung_smdk4412-d28232b461b8d54b09e59325dbac8b0913ce2049.tar.gz kernel_samsung_smdk4412-d28232b461b8d54b09e59325dbac8b0913ce2049.tar.bz2 | |
iwlwifi: fix scan abort
Fix possible double priv->mutex lock introduced by commit
a69b03e941abae00380fc6bc1877fb797a1b31e6
"iwlwifi: cancel scan watchdog in iwl_bg_abort_scan" .
We can not call cancel_delayed_work_sync(&priv->scan_check) with
priv->mutex locked because workqueue function iwl_bg_scan_check()
take that lock internally.
We do not need to synchronize when canceling priv->scan_check work.
We can avoid races (sending double abort command or send no
command at all) using STATUS_SCAN_ABORT bit. Moreover
current iwl_bg_scan_check() code seems to be broken, as
we should not send abort commands when currently aborting.
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
CC: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/mac80211/work.c')
0 files changed, 0 insertions, 0 deletions