[SERVER-30948] Add protection against releasing lock manager RAII objects out of order Created: 05/Sep/17 Updated: 06/Dec/22 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
One assumption for the RAII database lock types was that destruction order is always the reverse of construction order. However, with increasing usage of unique_ptr and boost::optional for more dynamic locking, we need additional checking that locking semantics are not violated. |