Fix use-after-free ClockSourceMock bug in transaction_coordinator_test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • ALL
    • Sharding 2020-08-24
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In transaction_coordinator_test, a ClockSourceMock gets associated to a service context that is already used by the WaitForMajorityService.

      As a result, it is potentially possible that a pointer to the original service context's ClockSource is used when waiting on an operation context instantiated before the ClockSourceMock.

      Check BF-17382 for additional details.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: