From: Pauli Date: Fri, 11 Jun 2021 09:10:49 +0000 (+1000) Subject: doc: add note to indicate that the OBJ_ functions were not thread safe in 3.0 X-Git-Tag: openssl-3.2.0-alpha1~3528 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b66b024cf7124c9639011b27b70a082e3bc3d269;p=thirdparty%2Fopenssl.git doc: add note to indicate that the OBJ_ functions were not thread safe in 3.0 Also remove OBJ_thread from the list of non-threadsafe functions. Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/15713) --- diff --git a/doc/man7/openssl-threads.pod b/doc/man7/openssl-threads.pod index 56cc638e1b8..7f29a327ac6 100644 --- a/doc/man7/openssl-threads.pod +++ b/doc/man7/openssl-threads.pod @@ -73,8 +73,8 @@ For implicit global state or singletons, thread-safety depends on the facility. The L and related API's have their own lock, while L assumes the underlying platform allocation will do any necessary locking. -Some API's, such as L and related, or L -do no locking at all; this can be considered a bug. +Some API's, such as L and related do no locking at all; +this can be considered a bug. A separate, although related, issue is modifying "factory" objects when other objects have been created from that.