Coverity analysis defect 150863: Thread deadlock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines, Storage Engines - Server Integration
    • ALL
    • StressiSESI - 2025-09-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Thread deadlock

      Two threads will be stuck waiting forever if each holds a lock the other needs to acquire. Threads may try to acquire two locks in different orders, potentially causing deadlock
      /src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp:1378: ORDER_REVERSAL 150863 Calling "lock_guard" acquires lock "mongo::WiredTigerKVEngine._oplogPinnedByBackupMutex" while holding lock "mongo::WiredTigerBackup.wtBackupDupCursorMutex" (count: 1 / 2).

            Assignee:
            Nick Beckenham
            Reporter:
            Coverity Collector User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: