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

Coverity analysis defect 100779: Thread deadlock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding
    • ALL
    • Sharding 2017-10-02

    Description

      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)

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            xgen-internal-coverity Coverity Collector User
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: