[openssl/openssl] fb5e8b: Provide independent lock failure signal on cmp_exc...
"'Neil Horman' via openssl-commits" <[email protected]>
| Newsgroups | gmane.comp.encryption.openssl.cvs |
|---|---|
| Message-ID | <openssl/openssl/push/refs/heads/master/[email protected]> |
Branch: refs/heads/master
Home: https://github.com/openssl/openssl
Commit: fb5e8bed5df5a73ce7b45acb6b7e4f0f7ba62916
https://github.com/openssl/openssl/commit/fb5e8bed5df5a73ce7b45acb6b7e4f0f7ba62916
Author: Neil Horman <[email protected]>
Date: 2026-06-09 (Tue, 09 Jun 2026)
Changed paths:
M crypto/rand/rand_lib.c
M crypto/threads_none.c
M crypto/threads_pthread.c
M crypto/threads_win.c
M doc/man3/CRYPTO_THREAD_run_once.pod
M include/openssl/crypto.h.in
Log Message:
-----------
Provide independent lock failure signal on cmp_exch_ptr
Our CRYPTO atomic api has a somewhat consistent problem in that its
possible in the case where locking fails to return an error while the
actual operation (store_int, store_ptr, etc), actually succeded.
cmp_exch is somewhat special here in that we may really need to know
independently if the function failed due to lock failure and if the
exchange occured (so we can know the output value of *expect). Add a
separate parameter to allow callers to be informed of these statuses
independently.
Reviewed-by: Norbert Pocs <[email protected]>
Reviewed-by: Nikola Pajkovsky <[email protected]>
MergeDate: Tue Jun 9 17:46:07 2026
(Merged from https://github.com/openssl/openssl/pull/31319)
To unsubscribe from these emails, change your notification settings at https://github.com/openssl/openssl/settings/notifications
--
You received this message because you are subscribed to the Google Groups "openssl-commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-commits/openssl/openssl/push/refs/heads/master/037ed1-fb5e8b%40github.com.