stun: make Agent's closed field thread-safe with Mutex #726
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
This commit wraps the `closed` boolean field in the STUN Agent with a Mutex to ensure thread-safety when the Agent is accessed from multiple threads concurrently. Signed-off-by: Xiaobo Liu <[email protected]>
rainliu
requested changes
Sep 4, 2025
Member
rainliu
left a comment
rainliu
left a comment
There was a problem hiding this comment.
I don’t see the reason why need mutex for this? Any example or test shows such concerns?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This commit wraps the
closedboolean field in the STUN Agent with a Mutex to ensure thread-safety when the Agent is accessed from multiple threads concurrently.