Commit fe8199ba authored by Rich Salz's avatar Rich Salz
Browse files

Add warnings to thread doc. 



Thanks to Yun Jiang for pointing this out.

Reviewed-by: default avatarRichard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5164)
parent d3736a65

doc/crypto/threads.pod

+6 −2
Original line number Diff line number Diff line
@@ -63,9 +63,13 @@ CRYPTO_destroy_dynlockid, CRYPTO_lock - OpenSSL thread support 


=head1 DESCRIPTION



OpenSSL can safely be used in multi-threaded applications provided

that at least two callback functions are set, locking_function and

OpenSSL can generally be used safely in multi-threaded applications provided

that at least two callback functions are set, the locking_function and

threadid_func.

Note that OpenSSL is not completely thread-safe, and unfortunately not all

global resources have the necessary locks.

Further, the thread-safety does not extend to things like multiple threads

using the same B<SSL> object at the same time.



locking_function(int mode, int n, const char *file, int line) is

needed to perform locking on shared data structures.