[SERVER-84120] Data race in waitForReadConcernImpl Created: 12/Dec/23 Updated: 03/Jan/24 Resolved: 03/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sean Zimmerman | Assignee: | Sean Zimmerman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2023-12-25, Repl 2024-01-08 | ||||
| Participants: | |||||
| Linked BF Score: | 120 | ||||
| Description |
|
When setting the cached oplog Collection pointer in local_oplog_info we do so under the protection of the global lock. When we read the pointer we are not under lock which can lead to a data race. |
| Comments |
| Comment by Githook User [ 03/Jan/24 ] |
|
Author: {'name': 'seanzimm', 'email': '102551488+seanzimm@users.noreply.github.com', 'username': 'seanzimm'}Message: GitOrigin-RevId: 6532f833d02fe694d375f19e8c857b10f46de05e |
| Comment by Louis Williams [ 12/Dec/23 ] |
|
We should not hold a lock while doing a blocking wait, as this can lead to deadlocks. |