summaryrefslogtreecommitdiffstats
path: root/third_party/rust/bytes-0.4.12/ci/tsan
diff options
context:
space:
mode:
Diffstat (limited to 'third_party/rust/bytes-0.4.12/ci/tsan')
-rw-r--r--third_party/rust/bytes-0.4.12/ci/tsan28
1 files changed, 28 insertions, 0 deletions
diff --git a/third_party/rust/bytes-0.4.12/ci/tsan b/third_party/rust/bytes-0.4.12/ci/tsan
new file mode 100644
index 0000000000..9cc54841bf
--- /dev/null
+++ b/third_party/rust/bytes-0.4.12/ci/tsan
@@ -0,0 +1,28 @@
+# TSAN suppressions file for `bytes`
+
+# TSAN does not understand fences and `Arc::drop` is implemented using a fence.
+# This causes many false positives.
+race:Arc*drop
+race:arc*Weak*drop
+
+# `std` mpsc is not used in any Bytes code base. This race is triggered by some
+# rust runtime logic.
+race:std*mpsc_queue
+
+# Some test runtime races. Allocation should be race free
+race:alloc::alloc
+
+# Not sure why this is warning, but it is in the test harness and not the library.
+race:TestEvent*clone
+race:test::run_tests_console::*closure
+
+# Probably more fences in std.
+race:__call_tls_dtors
+
+# `is_inline_or_static` is explicitly called concurrently without synchronization.
+# The safety explanation can be found in a comment.
+race:Inner::is_inline_or_static
+
+# This ignores a false positive caused by `thread::park()`/`thread::unpark()`.
+# See: https://github.com/rust-lang/rust/pull/54806#issuecomment-436193353
+race:pthread_cond_destroy