Fix unsynchronized uses of CurOp member variables

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-48970, TSAN reports unsynchronized uses of _start in CurOp here and here. It's possible that there are more private members of CurOp with similar synchronization problems that are hidden behind the current failure on _start described, so I've named this ticket to cover any subsequent failures in CurOp as well.

            Assignee:
            Justin Seyster
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: