Re: [PATCH] Wrong list_lock argument in rose_node seqops | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
From: Bernard Pidoux <bpidoux@xxxxxxx> Date: Wed, 30 Apr 2008 22:08:56 +0200 > 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@xxxxxxxxx> Applied, good catch. Thanks Bernard. -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Linux Newbie] [Kernel Newbies] [Memory] [Security] [Netfilter] [Linux Admin] [Bugtraq] [Rubini] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [ARM Linux Kernel] [Linux Networking] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Linux Resources]
![]() |