-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Service Arch
-
N&O Prioritized List
In SERVER-88159, we describe an issue and cases in practice where the use of diagnostic latches inhibits TSAN's ability to find lock-order inversions it would otherwise find, when the same program is run in the same environment using standard library mutexes.
In that ticket, we changed the TSAN configuration to use standard library mutexes to get additional coveredge, and documented all of the new inversions/bugs we found. We wanted to do this to increase coverage, considering we are shipping production with diagnostic latches disabled now, and may remove diagnostic latches entirely.
If we don't remove them, or build a replacement, we should get a deeper understanding into the root cause of the negative interaction between diagnostic latches and tsan (i.e. what extra memory barriers are diagnostic latches adding exactly, or is it related to their slowness, etc). This ticket tracks doing that investigation.
- depends on
-
SERVER-90745 Improve observability for mutex contention
- Closed
- related to
-
SERVER-88159 mongo::Mutex masks TSAN's ability to detect a lock order inversion
- Closed
-
SERVER-90429 Remove diagnostic latches
- Closed
-
SERVER-90745 Improve observability for mutex contention
- Closed