[SERVER-40084] Prevent readers from reading garbage/stale value from global_lock_acquisition_tracker. Created: 12/Mar/19 Updated: 29/Oct/23 Resolved: 28/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | A. Jesse Jiryu Davis |
| 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 2019-04-08 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, when we modify GlobalLockAcquisitionTracker:_globalLockMode, there is a possibility that the step down thread is reading its value concurrently. In order to avoid the step down thread from reading a garbage/stale value, make GlobalLockAcquisitionTracker:_globalLockMode as an AtomicWord<unsigned char>. |
| Comments |
| Comment by Judah Schvimer [ 17/Apr/19 ] |
|
Between the above commits there was this revert: Message: Revert " This reverts commit d99db775dbf73e27bd20e402f26f068dc199203d. |
| Comment by Githook User [ 17/Apr/19 ] |
|
Author: {'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}Message: Includes |
| Comment by Githook User [ 28/Mar/19 ] |
|
Author: {'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis'}Message: Includes |