[SERVER-48753] [4.4] '_abortIndexBuildsAndDropCollection()' should verify that the database exists after acquiring its lock Created: 11/Jun/20  Updated: 29/Oct/23  Resolved: 12/Jun/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 4.4.0-rc9
Fix Version/s: 4.4.0-rc10

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:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-06-29
Participants:
Linked BF Score: 25

 Description   

To prevent a segmentation fault, we need to check that the database exists after acquiring the database lock here otherwise this can crash if the database is non-existent by trying to get the profiling level.

This doesn't affect the master branch due to SERVER-47803.



 Comments   
Comment by Githook User [ 11/Jun/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-48753 '_abortIndexBuildsAndDropCollection()' should verify that the database exists after acquiring its lock
Branch: v4.4
https://github.com/mongodb/mongo/commit/3d37a082d3799f4b25738c7972c48febcb1d1406

Generated at Thu Feb 08 05:17:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.