-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Not Applicable
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-09-12
-
5
It turned out that TSAN doesn't detect synchronization that were made through stanalone barriers. The scope of this ticket is to find the best way to solve warnings caused by standalone barriers. Currently the approaches that I have on my mind are:
-
- Use annotation API (case-by-case solution under TSAN macro)
- Use atomics operations under TSAN (case-by-case solution under TSAN macro)
- Suppress warnings if there is no sync issue
That's the second part for the TSAN instrumentation investigation, the first one was done as a part of WT-15031