diff options
| author | Vasanthakumar Thiagarajan <[email protected]> | 2011-11-01 16:38:50 +0530 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2011-11-11 12:59:00 +0200 |
| commit | 11f6e40d9f21767a9090e4e559d3c63edf25e6c0 (patch) | |
| tree | c3fd39804436cc897756271f3fd1e6ba0d2a53db /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | b4b2a0b116d79510640622a5f28f219065e61b03 (diff) | |
ath6kl: Fix lockdep warning
The following is the lockdep warning which detects possible
deadlock condition with the way ar->lock and ar->list_lock
are being used.
(&(&ar->lock)->rlock){+.-...}, at: [<ffffffffa0492d13>] ath6kl_indicate_tx_activity+0x83/0x110 [ath6kl]
but this lock took another, SOFTIRQ-unsafe lock in the past:
(&(&ar->list_lock)->rlock){+.+...}
and interrupts could create inverse lock ordering between them.
other info that might help us debug this:
Possible interrupt unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&(&ar->list_lock)->rlock);
local_irq_disable();
lock(&(&ar->lock)->rlock);
lock(&(&ar->list_lock)->rlock);
<Interrupt>
lock(&(&ar->lock)->rlock);
*** DEADLOCK ***
softirqs have to be disabled when acquiring ar->list_lock to avoid
the above deadlock condition. When the above warning printed the
interface is still up and running without issue.
Reported-by: Kalle Valo <[email protected]>
Signed-off-by: Vasanthakumar Thiagarajan <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions