netdev - Re: [PATCH] sctp: lock_sock_nested in sctp_sock

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <46802460.3080303@linux.intel.com>
Date:	Mon, 25 Jun 2007 13:24:00 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Vlad Yasevich <vladislav.yasevich@...com>
CC:	Zach Brown <zach.brown@...cle.com>,
	lksctp-developers@...ts.sourceforge.net, netdev@...r.kernel.org
Subject: Re: [PATCH] sctp: lock_sock_nested in sctp_sock_migrate

Vlad Yasevich wrote:
> Hm... This is another case of of two different sockets taking the same lock...
> 
> Arjan,  did this every get fixed, or is the nested locking the right solution
> to this?
> 

for this specific case it's ok and the nested solution is right.
In the general case it's obviously not safe to take the locks of two 
sockets in "unspecified" order....
-
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