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

initializeOperationSessionInfo should take the client lock while writing lsid

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.13
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • Platforms 2017-09-11
    • 0

      initializeOperationSessionInfo is called without the client lock, which can cause it to do dirty partial writes to sessionId and txnNumber.

      This can cause data races with readers operating under the lock, causing them to see partial writes

            Assignee:
            mira.carey@mongodb.com Mira Carey
            Reporter:
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: