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

Future::isReady() should use memory_order_acquire

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.1
    • None
    • Internal Code
    • None
    • Fully Compatible
    • ALL
    • Platforms 2018-07-02

    Description

      While the rationale for making it relaxed is probably valid for external callers, an internal caller[1] is already using it incorrectly. Rather than fixing the internal caller, it seems easier and less bug-prone to just make isReady() do an acquire-load.

      [1] That method is only called from its unittest at the moment, so there is no bug in the shipping binaries.

      Attachments

        Activity

          People

            mathias@mongodb.com Mathias Stearn
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: