CursorManager attempts to dispose of aggregation cursors while holding partitioned lock, which leads to deadlock

Attempting to acquire a LockManager lock while holding a mutex is prone to deadlock. The CursorManager::killCursor() function locks the partition of CursorManager::_cursorMap corresponding to the specified cursor id. While holding the mutex, it calls ClientCursor::dispose(), which for an aggregation cursor attempts to acquire the collection lock in DocumentSourceCursor::cleanupExecutor() as part of DocumentSourceCursor::doDispose(). The "listCollections" and "listIndexes" commands hold the collection lock when attempting to call CursorManager::registerCursor(), forming the other edge of the deadlock cycle.

• https://github.com/mongodb/mongo/blob/r3.7.3/src/mongo/db/commands/list_collections.cpp#L343
• https://github.com/mongodb/mongo/blob/r3.7.3/src/mongo/db/commands/list_indexes.cpp#L196