diff options
| author | Pauli <pauli@openssl.org> | 2021-06-11 19:10:49 +1000 |
|---|---|---|
| committer | Tomas Mraz <tomas@openssl.org> | 2022-11-09 15:28:46 +0100 |
| commit | cd0cc4911f88f39f97dd13791b59a2d22463e663 (patch) | |
| tree | 33f122226da30f3056e7d696a71b254fffa6b7a3 /doc/man7 | |
| parent | a5d27c2907ed9658df228dc0b3b5743e20f1557f (diff) | |
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 <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15713)
(cherry picked from commit b66b024cf7124c9639011b27b70a082e3bc3d269)
Reviewed-by: Hugo Landau <hlandau@openssl.org>
Diffstat (limited to 'doc/man7')
| -rw-r--r-- | doc/man7/openssl-threads.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man7/openssl-threads.pod b/doc/man7/openssl-threads.pod index 56cc638e1b..7f29a327ac 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<CRYPTO_secure_malloc(3)> and related API's have their own lock, while L<CRYPTO_malloc(3)> assumes the underlying platform allocation will do any necessary locking. -Some API's, such as L<NCONF_load(3)> and related, or L<OBJ_create(3)> -do no locking at all; this can be considered a bug. +Some API's, such as L<NCONF_load(3)> 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. |