[SERVER-36711] BackupCursorService error case double-locks mutex Created: 17/Aug/18  Updated: 29/Oct/23  Resolved: 17/Aug/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.3

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-08-27
Participants:
Linked BF Score: 2

 Description   

Opening a backup cursor acquires a mutex to protect some basic state. After opening a cursor, the state is changed. However, the opening process can still fail with uasserts, so a scopeguard is registered to undo the opening operation. But, closing the backup cursor also acquires the state protecting mutex.



 Comments   
Comment by Githook User [ 17/Aug/18 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-36711: Avoid double locking mutex in ScopeGuard destruction.
Branch: master
https://github.com/mongodb/mongo/commit/9fd731be471c3d0f40bf5208f2bdd3923c9ea3e8

Generated at Thu Feb 08 04:43:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.