diff options
| author | Tor Brede Vekterli <vekterli@yahooinc.com> | 2022-05-18 15:44:05 +0000 |
|---|---|---|
| committer | Tor Brede Vekterli <vekterli@yahooinc.com> | 2022-05-18 15:44:05 +0000 |
| commit | 15260a85ed364f887a84dbd36a291ef028e94fd3 (patch) | |
| tree | bcf9669e6b5a0b0fcf80997978712082182acc4e /tsan-suppressions.txt | |
| parent | 2c9cb8159adaced573fd1e34689e533946feea85 (diff) | |
Add TSan suppressions for some OpenSSL internals
Diffstat (limited to 'tsan-suppressions.txt')
| -rw-r--r-- | tsan-suppressions.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/tsan-suppressions.txt b/tsan-suppressions.txt index f637e1b4ead..00cd7fe9a3a 100644 --- a/tsan-suppressions.txt +++ b/tsan-suppressions.txt @@ -40,3 +40,13 @@ race:llvm::sys::SmartMutex<true>::lock race:re2::Prog::GetDFA race:re2::DFA::DFA + +# Non-TSAN instrumented OpenSSL may trigger warnings when many threads are attempting +# to create TLS connections at once in a newly started process. This appears to be related +# to implicit init-once semantics of internal OpenSSL datastructures, though the TSAN report +# stack frames are truncated and don't show the full picture. +# When a TSAN-instrumented OpenSSL build is used, the error does not manifest itself. +# This implies that it's likely caused by a lack of instrumentation of atomic operations +# (acquire-load in double-checked locking etc). +race:ASN1_STRING_cmp +race:ASN1_STRING_set |