mirror of
https://github.com/tokio-rs/tokio.git
synced 2025-09-25 12:00:35 +00:00

This also adds a filter for another treiber stack expected data race. The race is expected as part of the algorithm.
34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
# TSAN suppressions file for Tokio
|
|
|
|
# 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 Tokio code base. This race is triggered by some
|
|
# rust runtime logic.
|
|
race:std*mpsc_queue
|
|
|
|
# Probably more fences in std.
|
|
race:__call_tls_dtors
|
|
|
|
# The crossbeam deque uses fences.
|
|
race:crossbeam_deque
|
|
|
|
# This is excluded as this race shows up due to using the stealing features of
|
|
# the deque. Unfortunately, the implementation uses a fence, which makes tsan
|
|
# unhappy.
|
|
#
|
|
# TODO: It would be nice to not have to filter this out.
|
|
race:try_steal_task
|
|
|
|
# This filters out expected data race in the treiber stack implementations.
|
|
# Treiber stacks are inherently racy. The pop operation will attempt to access
|
|
# the "next" pointer on the node it is attempting to pop. However, at this
|
|
# point it has not gained ownership of the node and another thread might beat
|
|
# it and take ownership of the node first (touching the next pointer). The
|
|
# original pop operation will fail due to the ABA guard, but tsan still picks
|
|
# up the access on the next pointer.
|
|
race:Backup::next_sleeper
|
|
race:WorkerEntry::set_next_sleeper
|