usrsock: add REMOTE_CLOSED event handler to connect #7652
Merged
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.
Summary
when usrsock client try to connect usrsock server local_loop socket with an invalid port, server cannot find a listener conn to handle this connet request, then it will response a TCP_RESET packet via nuttx existing processing, when before conn recv this RESET packet, it will trigger usrsock_rpmsg_server poll return and send REMOTE_CLOSE event to usrsock client.
so usrsock connect_event fucntion need handle this event.
Impact
usrsock
Testing
Internal test