UDP worker: conn.updateActivity() should be executed in Lock
#4910
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
patterniha
changed the title
conn.updateActivity() should be executed in Lock
Collaborator
Author
|
CC @RPRX |
This was referenced Jul 21, 2025
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.
#4909 (comment)
because updateActivity() runs out of udpworker-Lock:
suppose exactly after 2 minutes of inactivity a packet is received from inbound, so it is possible we create a new-outbound-connection for that but we don't update udpconn-activity and close that.
this cause we ignore the active-outbound-connection by mistake and create new one for next-received-packet.
///
possible is possible, even with a very low probability.