commit | 0d29302155f49d4d5c7fa34a658ad5a97dd013a2 | [log] [tgz] |
---|---|---|
author | mpage <mpage@meta.com> | Wed Apr 17 10:19:28 2024 -0700 |
committer | GitHub <noreply@github.com> | Wed Apr 17 17:19:28 2024 +0000 |
tree | 84ab95a6fa91eb9c4c600fd452e9b6495529bb39 | |
parent | b6c62c79e7d9592ca1ea6b93f6ce3dd3829939d0 [diff] |
gh-117657: Quiet erroneous TSAN reports of data races in `_PySeqLock` (#117955) Quiet erroneous TSAN reports of data races in `_PySeqLock` TSAN reports a couple of data races between the compare/exchange in `_PySeqLock_LockWrite` and the non-atomic loads in `_PySeqLock_{Abandon,Unlock}Write`. This is another instance of TSAN incorrectly modeling failed compare/exchange as a write instead of a load.