Coverity analysis defect 100779: Thread deadlock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • ALL
    • Sharding 2017-10-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Threads may try to acquire two locks in different orders, potentially causing deadlock

      Defect 100779 (STATIC_C)
      Checker ORDER_REVERSAL (subcategory none)
      File: /src/mongo/db/logical_clock.cpp
      Function mongo::LogicalClock::reserveTicks(unsigned long)

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Coverity Collector User
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: