netdev - [PATCH] [ROSE] finding a connected ROSE neighbor node

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-next>] [day] [month] [year] [list]

Date:	Fri, 14 Dec 2007 23:23:48 +0100
From:	Bernard Pidoux <pidoux@....jussieu.fr>
To:	David Miller <davem@...emloft.net>
CC:	Alexey Dobriyan <adobriyan@...il.com>,
	Ralf Baechle DL5RB <ralf@...ux-mips.org>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: [PATCH] [ROSE] finding a connected ROSE neighbor node

Hi,

This patch introduces a test to determine if a neighbor node with a 
given ROSE address is already connected and if so returns its address.
The previous test was only performed on timer t0 and not on parameter 
restarted that is true when a node is connected.
Also, previously the test was not performed on the whole node list.
A new function __rose_get_neigh() is introduced to cure a spin lock 
conflict related to rose_node_list_lock.

signed off by Alexey Dobriyan,adobriyan@...il.com
signed off by Bernard Pidoux, f6bvp @ amsat.org

View attachment "rose-2.6.24-rc5.patch2" of type "text/plain" (2756 bytes)