ClockSource::waitForConditionUntil shouldn't use unique_lock out of line

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Service Arch 2019-10-21
    • 21
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have a somewhat dubious pattern here where it is possible for an alarm to invoke inline and attempt to hold a lock that was already acquired. The lock use itself isn't necessary, because condition variables are surprisingly atomic.

            Assignee:
            Benjamin Caimano (Inactive)
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: