diff options
| author | Javier Cardona <javier@cozybit.com> | 2011-05-03 16:57:16 -0700 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2011-05-11 14:50:35 -0400 |
| commit | 9b84b80891e5e25ae21c855bb135b05274125a29 (patch) | |
| tree | 1e833eb357f66aba37980b240de48671eec900a6 /drivers/rtc/rtc-max6900.c | |
| parent | 9ca99eeca0cfe839c481f3350988e9ed94188567 (diff) | |
| download | linux-stable-9b84b80891e5e25ae21c855bb135b05274125a29.tar.gz linux-stable-9b84b80891e5e25ae21c855bb135b05274125a29.tar.bz2 linux-stable-9b84b80891e5e25ae21c855bb135b05274125a29.zip | |
mac80211: Fix locking bug on mesh path table access
The mesh and mpp path tables are accessed from softirq and workqueue
context so non-irq locking cannot be used. Or at least that's what
PROVE_RCU seems to tell us here:
[ 431.240946] =================================
[ 431.241061] [ INFO: inconsistent lock state ]
[ 431.241061] 2.6.39-rc3-wl+ #354
[ 431.241061] ---------------------------------
[ 431.241061] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
[ 431.241061] kworker/u:1/1423 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 431.241061] (&(&newtbl->hashwlock[i])->rlock){+.?...}, at:
[<c14671bf>] mesh_path_add+0x167/0x257
Signed-off-by: Javier Cardona <javier@cozybit.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/rtc/rtc-max6900.c')
0 files changed, 0 insertions, 0 deletions