Fix data race with CurOp if a command has a clientKeyOperation field

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • ALL
    • Service Arch 2023-11-27, Service Arch 2023-12-11
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If a command with a clientOperationKey field and a $currentOp aggregation operation are running at the same time, there's a potential data race on the OperationContext member, _opKey, where the service entry point thread writes it here (without taking the Client lock), while the CurOp thread reads it here (while holding the Client lock).

            Assignee:
            Ryan Berryhill
            Reporter:
            Erwin Pe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: