GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||
GeezerVison is showing github.com — gh-117657: Quiet erroneous TSAN reports of data races in `_PySeqLock` by mpage · Pull Request #117955 · python/cpython Conversation
|
| else if (_Py_atomic_compare_exchange_uint32(&seqlock->sequence, &prev, prev + 1)) { |
and the non-atomic loads in _PySeqLock_AbandonWrite (example race):
Lines 493 to 495 in a23fa33
| void _PySeqLock_AbandonWrite(_PySeqLock *seqlock) | |
| { | |
| uint32_t new_seq = seqlock->sequence - 1; |
and _PySeqLock_UnlockWrite (example race):
Lines 500 to 502 in a23fa33
| void _PySeqLock_UnlockWrite(_PySeqLock *seqlock) | |
| { | |
| uint32_t new_seq = seqlock->sequence + 1; |
This is another instance of TSAN incorrectly modeling failed compare/exchange as a write instead of a load.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.