Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-102360

Coverity analysis defect 168194: Thread deadlock

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • ALL
    • N&O 2025-03-31
    • 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
      /data/mci/8df2c396557fb87fa29efdf21060b868/bazel_cache/18545ad5d47fdc81034b726533d3cf62/execroot/_main_/src/mongo/db/default_baton.cpp:93: ORDER_REVERSAL 168194 Calling "unique_lock" acquires lock "mongo::DefaultBaton._mutex". [Note: The source code implementation of the function has been overridden by a builtin model.]

            Assignee:
            joseph.prince@mongodb.com Joseph Prince
            Reporter:
            xgen-internal-coverity Coverity Collector User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None