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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • None
    • None
    • None
    • Service Arch
    • Fully Compatible
    • ALL
    • Service Arch 2023-11-27, Service Arch 2023-12-11
    • 3

    Description

      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).

      Attachments

        Activity

          People

            ryan.berryhill@mongodb.com Ryan Berryhill
            erwin.pe@mongodb.com Erwin Pe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: