Operational Defect Database

BugZero found this defect 2504 days ago.

MongoDB | 375447

[SERVER-28860] Coverity analysis defect 100781: Thread deadlock

Last update date:

10/27/2023

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

Threads may try to acquire two locks in different orders, potentially causing deadlock Defect 100781 (STATIC_C) Checker ORDER_REVERSAL (subcategory none) File: /src/mongo/db/repl/database_cloner.cpp Function mongo::repl::DatabaseCloner::_collectionClonerCallback(const mongo::Status &, const mongo::NamespaceString &)

Top User Comments

william.schultz commented on Thu, 6 Jul 2017 16:26:43 +0000: The Coverity analysis claims that we recursively acquire the DatabaseCloner::_mutex in DatabaseCloner::_collectionClonerCallback when we call DatabaseCloner::_finishCallback_inlock which calls DatabaseCloner::_finishCallback_inlock. However, DatabaseCloner::_finishCallback_inlock always unlocks the lock first if necessary, avoiding this scenario.

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...