QuasarApp/openssl
4
0
Fork 0
mirror of https://github.com/QuasarApp/openssl.git synced 2025-05-14 10:29:42 +00:00
Code Issues Projects Releases Wiki Activity

Add warnings to thread doc.

Browse Source 
Thanks to Yun Jiang for pointing this out.

Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5164)
This commit is contained in:
Rich Salz 2018-01-24 17:28:45 -05:00
parent d3736a65ba
commit fe8199badf
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/crypto/threads.pod
View File

@ -63,9 +63,13 @@ CRYPTO_destroy_dynlockid, CRYPTO_lock - OpenSSL thread support
=head1 DESCRIPTION =head1 DESCRIPTION
OpenSSL can safely be used in multi-threaded applications provided OpenSSL can generally be used safely in multi-threaded applications provided
that at least two callback functions are set, locking_function and that at least two callback functions are set, the locking_function and
threadid_func. 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 locking_function(int mode, int n, const char *file, int line) is
needed to perform locking on shared data structures. needed to perform locking on shared data structures.