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

initializeOperationSessionInfo should take the client lock while writing lsid

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.13
    • Internal Code
    • None
    • Fully Compatible
    • ALL
    • Platforms 2017-09-11
    • 0

    Description

      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

      Attachments

        Activity

          People

            jason.carey@mongodb.com Jason Carey
            jason.carey@mongodb.com Jason Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: