From fe8199badfce9ffccd0e1d9c245c4cdd8d412ef1 Mon Sep 17 00:00:00 2001 From: Rich Salz Date: Wed, 24 Jan 2018 17:28:45 -0500 Subject: [PATCH] Add warnings to thread doc. Thanks to Yun Jiang for pointing this out. Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/5164) --- 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 dc0e9391dc..30c19b815f 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 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. -- 2.40.0