netdev - Re: [PATCH] Wrong list_lock argument in rose

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080502.170334.97648357.davem@davemloft.net>
Date:	Fri, 02 May 2008 17:03:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bpidoux@...e.fr
Cc:	ralf@...ux-mips.org, netdev@...r.kernel.org,
	linux-hams@...r.kernel.org
Subject: Re: [PATCH] Wrong list_lock argument in rose_node seqops

From: Bernard Pidoux <bpidoux@...e.fr>
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@...at.org>

Applied, good catch.

Thanks Bernard.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html