Michal Kazior <[email protected]> writes: > This should prevent deadlock predicted by the > following splat: > > ====================================================== > [ INFO: possible circular locking dependency detected ] > 3.17.0-wl-ath+ #67 Not tainted > ------------------------------------------------------- > kworker/u32:1/7230 is trying to acquire lock: > (&ar->conf_mutex){+.+.+.}, at: [<ffffffffa040a57d>] > ath10k_scan_timeout_work+0x2d/0x50 [ath10k_core] > > but task is already holding lock: > ((&(&ar->scan.timeout)->work)){+.+...}, at: [<ffffffff8106dae1>] > process_one_work+0x151/0x470 > > which lock already depends on the new lock. >
[...] > *** DEADLOCK *** > > Reported-by: Marek Puzyniak <[email protected]> > Signed-off-by: Michal Kazior <[email protected]> Thanks, applied. -- Kalle Valo _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
