summaryrefslogtreecommitdiff
path: root/etc/tsan.suppressions
diff options
context:
space:
mode:
authorRyan Egesdahl <ryan.egesdahl@mongodb.com>2020-06-30 22:26:26 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2020-07-07 19:30:46 +0000
commit6a8d8eb4da7705e9bbf46890051301a9e8ef3e90 (patch)
treee3ad40ce77904412bdacd81c78509903d285bc09 /etc/tsan.suppressions
parentc0c6890f477a9faa239dada415259fe57a2c6d7b (diff)
downloadmongo-6a8d8eb4da7705e9bbf46890051301a9e8ef3e90.tar.gz
SERVER-49078 Suppress TSAN reports for AS-unsafe calls in signal handlers
Two functions we call in signal handlers call malloc() down the line. Because these functions generally happen while the thread was dying, we will permit the AS-unsafe call, especially since we've never had any problems with any allocators we've ever used.
Diffstat (limited to 'etc/tsan.suppressions')
-rw-r--r--etc/tsan.suppressions7
1 files changed, 7 insertions, 0 deletions
diff --git a/etc/tsan.suppressions b/etc/tsan.suppressions
index 447d3cc3ad4..08da28be651 100644
--- a/etc/tsan.suppressions
+++ b/etc/tsan.suppressions
@@ -16,3 +16,10 @@ signal:src/mongo/unittest/death_test.cpp
# TODO: https://jira.mongodb.org/browse/SERVER-48599
race:src/third_party/wiredtiger/*
+# These functions call malloc() down the line while inside a signal handler.
+# Since we've never had problems with any of the allocators we use, and since
+# the process is going to exit in actual practice (unlike in some of our tests),
+# we are taking the calculated risk to allow AS-unsafe calls in our signal
+# handlers.
+signal:abruptQuitAction
+signal:abruptQuitWithAddrSignal