On Fri, 2010-06-25 at 21:43 +0100, Darryl Miles wrote: > Mark Phalan wrote: > > > Except setting up locking at library setup time is inherently racy and > > *cannot* be done safely. The *only* safe place to setup locking > > callbacks is from the application. libraries cannot safely setup the > > locking callbacks. > > Just to make it clear why this is a problem imagine two threads running > > on Solaris each concurrently dlopening a plugin. Each plugin is linked > > against OpenSSL and tries to be a good citizen by setting the locking > > callbacks. They have no way to synchronize and thus no way to avoid > > racing against each other. > > This is my point. This is possible even on Sparc without setting up > threading, please don't spread such misinformation.
Actually i thought I was agreeing with you... I was backing up your suggestion that more is needed from OpenSSL to more cleanly support threading. -M ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
