summaryrefslogtreecommitdiffstats
path: root/crypto/cryptomgr.c
diff options
context:
space:
mode:
authorJarek Poplawski <jarkao2@gmail.com>2008-02-12 06:26:43 +0100
committerDavid S. Miller <davem@davemloft.net>2008-02-13 02:53:32 +0100
commit4de211f1a279275c6c67d6e9b6b25513e46b0bb9 (patch)
treeb8e57f1000ed1d5ba0d93a8126a613ca6b3c7a7a /crypto/cryptomgr.c
parent[AX25] af_ax25: remove sock lock in ax25_info_show() (diff)
downloadlinux-4de211f1a279275c6c67d6e9b6b25513e46b0bb9.tar.xz
linux-4de211f1a279275c6c67d6e9b6b25513e46b0bb9.zip
[AX25] ax25_route: make ax25_route_lock BH safe
> ================================= > [ INFO: inconsistent lock state ] > 2.6.24-dg8ngn-p02 #1 > --------------------------------- > inconsistent {softirq-on-W} -> {in-softirq-R} usage. > linuxnet/3046 [HC0[0]:SC1[2]:HE1:SE0] takes: > (ax25_route_lock){--.+}, at: [<f8a0cfb7>] ax25_get_route+0x18/0xb7 [ax25] > {softirq-on-W} state was registered at: ... This lockdep report shows that ax25_route_lock is taken for reading in softirq context, and for writing in process context with BHs enabled. So, to make this safe, all write_locks in ax25_route.c are changed to _bh versions. Reported-by: Jann Traschewski <jann@gmx.de>, Signed-off-by: Jarek Poplawski <jarkao2@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/cryptomgr.c')
0 files changed, 0 insertions, 0 deletions