From f21b5b64cbbc279ef31389e6ae312690575187da Mon Sep 17 00:00:00 2001 From: Andy Polyakov Date: Sun, 29 Jul 2018 14:37:17 +0200 Subject: x509v3/v3_purp.c: re-implement lock-free check for extensions cache validity. Reviewed-by: Paul Dale Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/6786) --- crypto/x509v3/v3_purp.c | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'crypto/x509v3/v3_purp.c') diff --git a/crypto/x509v3/v3_purp.c b/crypto/x509v3/v3_purp.c index d804106788..5a535e2ade 100644 --- a/crypto/x509v3/v3_purp.c +++ b/crypto/x509v3/v3_purp.c @@ -13,6 +13,7 @@ #include #include #include "internal/x509_int.h" +#include "internal/tsan_assist.h" static void x509v3_cache_extensions(X509 *x); @@ -353,6 +354,10 @@ static void x509v3_cache_extensions(X509 *x) X509_EXTENSION *ex; int i; + /* fast lock-free check, see end of the function for details. */ + if (tsan_load((TSAN_QUALIFIER int *)&x->ex_cached)) + return; + CRYPTO_THREAD_write_lock(x->lock); if (x->ex_flags & EXFLAG_SET) { CRYPTO_THREAD_unlock(x->lock); @@ -494,6 +499,12 @@ static void x509v3_cache_extensions(X509 *x) x509_init_sig_info(x); x->ex_flags |= EXFLAG_SET; CRYPTO_THREAD_unlock(x->lock); + /* + * It has to be placed after memory barrier, which is implied by unlock. + * Worst thing that can happen is that another thread proceeds to lock + * and checks x->ex_flags & EXFLAGS_SET. See beginning of the function. + */ + tsan_store((TSAN_QUALIFIER int *)&x->ex_cached, 1); } /*- -- cgit v1.2.3