[SERVER-53137] The CurOp constructor should initialize its variables prior to being added to the stack of active CurOp objects Created: 30/Nov/20 Updated: 29/Oct/23 Resolved: 01/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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: | Execution Team 2020-12-14 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
On L356, we call the constructor on L363 to add the CurOp object onto the stack of active CurOp objects before initializing its _lockStatsBase member variable. This is problematic as it makes the CurOp object available for external use before being fully initialized. For example, the currentOp command tries to access _lockStatsBase for all active CurOp objects. |
| Comments |
| Comment by Githook User [ 01/Dec/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |