Coverity analysis defect 176048: Value not atomically updated

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • CAR Team 2025-09-29
    • 1
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Value not atomically updated

      The result of the update will be determined by the interleaving of thread execution. Non-atomic update of a concurrently shared value
      /src/mongo/db/topology/add_shard_coordinator.cpp:350: ATOMICITY 176048 Locking "opCtx->_client".
      /src/mongo/db/topology/add_shard_coordinator.cpp:343: ATOMICITY 176048 Assigning data that might be protected by the lock to "database".
      /src/mongo/db/topology/add_shard_coordinator.cpp:350: ATOMICITY 176048 Unlocking "this->this->_docMutex". "database" might now be unreliable because other threads can now change the data that it depends on.
      /src/mongo/db/topology/add_shard_coordinator.cpp:350: ATOMICITY 176048 Locking "opCtx->_client" again.
      /src/mongo/db/topology/add_shard_coordinator.cpp:355: ATOMICITY 176048 Using an unreliable value of "database" inside the second locked section. If the data that "database" depends on was changed by another thread, this use might be incorrect.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Coverity Collector User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: