-
Notifications
You must be signed in to change notification settings - Fork 634
Lock before checking ares_event_thread::isup
#915
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.
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In theory, reads and writes to a boolean should always be atomic so a mutex shouldn't be needed. Plus in this case there's not much harm if |
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
bradh352
pushed a commit
that referenced
this pull request
Nov 9, 2024
TSAN is warning about a thread concurrency issue that doesn't actually matter if the operation isn't atomic as its an optimization in this code path to skip timeout processing if we're shutting down due to ares_destroy(). Fix By: Jiwoo Park (@jimmy-park)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found a missing lock protection inside the event thread loop.