Fix f7e390bd: getpeername() doesn't work on closed sockets #9213
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.
Motivation / Problem
I blindly assumed
getpeername()
works on sockets, opened or recently closed. I was wrong.Initially testing didn't show this, as I made a last minute change to this, and failed to test this specific flow.
Description
Store the real address we are connecting to in a map, so for debug statements we can show more useful information.
This is a bit more bookkeeping, so easier to mess up; but at least it is better than not knowing what failed exactly.
As extra bonus, found a few minor mistakes:
close
instead ofclosesocket
, and not cleaning the list on timeout, causing the sockets to be closed twice (absolutely no harm in doing that, just not useful).Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.