The branch OpenSSL_1_0_2-stable has been updated
via fe8199badfce9ffccd0e1d9c245c4cdd8d412ef1 (commit)
from d3736a65baadb369b2570bf85d7f966bc567e7ff (commit)
- Log -----------------------------------------------------------------
commit fe8199badfce9ffccd0e1d9c245c4cdd8d412ef1
Author: Rich Salz <[email protected]>
Date: Wed Jan 24 17:28:45 2018 -0500
Add warnings to thread doc.
Thanks to Yun Jiang for pointing this out.
Reviewed-by: Richard Levitte <[email protected]>
(Merged from https://github.com/openssl/openssl/pull/5164)
-----------------------------------------------------------------------
Summary of changes:
doc/crypto/threads.pod | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/crypto/threads.pod b/doc/crypto/threads.pod
index dc0e939..30c19b8 100644
--- a/doc/crypto/threads.pod
+++ b/doc/crypto/threads.pod
@@ -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.
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits
