Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid race that triggers timer too often #621

Merged
merged 1 commit into from
Mar 23, 2019
Merged

Avoid race that triggers timer too often #621

merged 1 commit into from
Mar 23, 2019

Commits on Mar 21, 2019

  1. Avoid race that triggers timer too often 

    The two distinct operations of acquiring and subsequent checking of a
timer have to be protected by one lock_guard against races with other
threads. The releasing of a timer has to be protected by the same lock.

Given this requirement there is no use for a second mutex.

Signed-off-by: Marko Durkovic <[email protected]>
    @durko @wjwwood
    durko authored and wjwwood committed Mar 21, 2019
    Configuration menu
    Copy the full SHA
    9a807c2 View commit details
    Browse the repository at this point in the history