[SERVER-70579] Unsynchronized access to ProgressMeter::_total field Created: 14/Oct/22 Updated: 31/Mar/23 Resolved: 31/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Matt Kneiser |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2022-12-26, Execution Team 2023-03-06, Execution Team 2023-04-03, Execution Team 2023-04-17 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 14 | ||||||||||||
| Description |
|
Reading and writing to the _total field in ProgressMeter can have a data race. For example, between two thread running in MultiIndexBlock and CurOp. |
| Comments |
| Comment by Matt Kneiser [ 31/Mar/23 ] |
|
There was only one hit on this TSAN failure in October. The tip of master looked fine, which made sense when I looked at the commit history and saw that the proper locking was added to these callers of ProgressMeter. |