diff options
| author | Pauli <pauli@openssl.org> | 2021-06-23 09:46:42 +1000 |
|---|---|---|
| committer | Pauli <pauli@openssl.org> | 2021-06-24 15:50:26 +1000 |
| commit | 0218bcdd3feab456135207c140998305df73ab7b (patch) | |
| tree | e28b95bb13927fb1756d739938151d6b5ca0bd08 /doc/man7/provider-base.pod | |
| parent | 13757e128378af79b3522002b4ae6b2a0678cf96 (diff) | |
doc: Document that the OBJ creation functions don't lock.
Neither OBJ_create() nor OBJ_add_sigid() use locks. They are not thread safe.
They can and will cause the other OBJ_ query functions to fail in mysterious
ways if called concurrently with them.
There is no problem calling multiple query functions concurrently.
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15865)
Diffstat (limited to 'doc/man7/provider-base.pod')
| -rw-r--r-- | doc/man7/provider-base.pod | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/man7/provider-base.pod b/doc/man7/provider-base.pod index 0eb2f5d243..5812ece7f8 100644 --- a/doc/man7/provider-base.pod +++ b/doc/man7/provider-base.pod @@ -264,6 +264,7 @@ It will treat as success the case where the OID already exists (even if the short name I<sn> or long name I<ln> provided as arguments differ from those associated with the existing OID, in which case the new names are not associated). +This function is not thread safe. The core_obj_add_sigid() function registers a new composite signature algorithm (I<sign_name>) consisting of an underlying signature algorithm (I<pkey_name>) @@ -277,6 +278,7 @@ to identify the object. It will treat as success the case where the composite signature algorithm already exists (even if registered against a different underlying signature or digest algorithm). It returns 1 on success or 0 on failure. +This function is not thread safe. CRYPTO_malloc(), CRYPTO_zalloc(), CRYPTO_memdup(), CRYPTO_strdup(), CRYPTO_strndup(), CRYPTO_free(), CRYPTO_clear_free(), |