8000 Thread safe access to `lookupTime` by Areson · Pull Request #185 · cirello-io/dynamolock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Thread safe access to lookupTime #185

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
Closed
wants to merge 1 commit into from
Closed

Thread safe access to lookupTime #185

wants to merge 1 commit into from

Conversation

Areson
Copy link
@Areson Areson commented Mar 23, 2023

When locks have both a heartbeat and a session monitor lookupTime can be accessed across multiple threads, leading to a race condition. This change adds a mutex around reading and writing this value to prevent this.

Fixes #184

@Areson
Thread safe access to lookupTime
c9abff7 
When locks have both a heartbeat and a session monitor `lookupTime` can be accessed across multiple threads, leading to a race condition. This change adds a mutex around reading and writing this value to prevent this.
@ucirello
Copy link
Collaborator

Fixed by 9b891ec

@ucirello ucirello closed this Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Race Condition on lock.lookupTime
2 participants
@Areson @ucirello
0