Add TSAN suppression for usrsctp

Both suppressions are related to the same lock and can be triggered
from 2 different API calls.
Since those calls are causing a significant amount of flaky tests,
I opted to suppress the issue for now, until we can either find a solution
upstream or replace usrsctp with DcSCTP.

Bug: webrtc:12823
Change-Id: I0ae49c94810264f94838b97781080cf5e6e4b24c
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/231136
Commit-Queue: Florent Castelli <orphis@webrtc.org>
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#34916}
This commit is contained in:
Florent Castelli 2021-09-03 13:41:53 +02:00 committed by WebRTC LUCI CQ
parent 4d6a76d781
commit c4152a3bb1

View file

@ -45,6 +45,11 @@ char kTSanDefaultSuppressions[] =
// https://code.google.com/p/webrtc/issues/detail?id=5151
"race:sctp_close\n"
// lock-order-inversion in usrsctp
// TODO(orphis): https://crbug.com/webrtc/12823
"deadlock:usrsctp_conninput\n"
"deadlock:usrsctp_connect\n"
// Potential deadlocks detected after roll in r6516.
// https://code.google.com/p/webrtc/issues/detail?id=3509
"deadlock:webrtc::test::UdpSocketManagerPosixImpl::RemoveSocket\n"