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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
