linux/net/rose
Bernard Pidoux f37f2c62a2 rose: Wrong list_lock argument in rose_node seqops
In rose_node_start() as well as in rose_node_stop() __acquires() and
spin_lock_bh() were wrongly passing rose_neigh_list_lock instead of
rose_node_list_lock arguments.

Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
2008-05-02 17:03:22 -07:00
..
Makefile
af_rose.c rose: Socket lock was not released before returning to user space 2008-04-19 18:41:51 -07:00
rose_dev.c [ROSE]: Trivial compilation CONFIG_INET=n case 2007-12-05 05:37:28 -08:00
rose_in.c [ROSE]: Supress sparse warnings 2008-01-28 15:02:44 -08:00
rose_link.c
rose_loopback.c
rose_out.c
rose_route.c rose: Wrong list_lock argument in rose_node seqops 2008-05-02 17:03:22 -07:00
rose_subr.c
rose_timer.c
sysctl_net_rose.c [NET]: Simple ctl_table to ctl_path conversions. 2008-01-28 15:01:07 -08:00