[SERVER-34010] allow LockManager to pass thread sanitizer tests Created: 20/Mar/18 Updated: 27/Oct/23 Resolved: 09/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Currently thread-analyzer detects potential race conditions, at least wrt. diagnostic tools. Analyze/fix these and do any additional work/annotation to ensure that the LockManager / Locker implementations are thread sanitizer clean. |
| Comments |
| Comment by Louis Williams [ 09/Oct/20 ] |
|
Closing because we have made fixes to the LockManager for the thread sanitizer, completed in |