diff options
| author | Arnd Bergmann <[email protected]> | 2011-07-01 17:30:00 -0700 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2011-07-01 17:30:00 -0700 |
| commit | 6e4e2f811bade330126d4029c88c831784a7efd9 (patch) | |
| tree | 03d365ae386b9a8f43c24483eb0455a73a96bf48 /net/lapb/lapb_timer.c | |
| parent | 60c2ce2b4facf28f569115a55e1f479eb12bd0f1 (diff) | |
6pack,mkiss: fix lock inconsistency
Lockdep found a locking inconsistency in the mkiss_close function:
> kernel: [ INFO: inconsistent lock state ]
> kernel: 2.6.39.1 #3
> kernel: ---------------------------------
> kernel: inconsistent {IN-SOFTIRQ-R} -> {SOFTIRQ-ON-W} usage.
> kernel: ax25ipd/2813 [HC0[0]:SC0[0]:HE1:SE1] takes:
> kernel: (disc_data_lock){+++?.-}, at: [<ffffffffa018552b>] mkiss_close+0x1b/0x90 [mkiss]
> kernel: {IN-SOFTIRQ-R} state was registered at:
The message hints that disc_data_lock is aquired with softirqs disabled,
but does not itself disable softirqs, which can in rare circumstances
lead to a deadlock.
The same problem is present in the 6pack driver, this patch fixes both
by using write_lock_bh instead of write_lock.
Reported-by: Bernard F6BVP <[email protected]>
Tested-by: Bernard F6BVP <[email protected]>
Signed-off-by: Arnd Bergmann <[email protected]>
Acked-by: Ralf Baechle<[email protected]>
Cc: [email protected]
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions