fix(tcp): reset FIN-WAIT data after receive shutdown - #5
Merged
fslongjin merged 2 commits intoMay 16, 2026
Merged
Conversation
Add an explicit receive-shutdown state to TCP sockets so users of the stack can model Linux/BSD close(2) orphan semantics. When the local receive half has been shut down and the socket is in FIN-WAIT-1 or FIN-WAIT-2, any peer payload that advances the receive sequence space now closes the socket and emits an active RST instead of being queued or answered with zero-window ACKs. Also add a focused regression test for FIN-WAIT receive-shutdown data. Signed-off-by: longjin <longjin@DragonOS.org>
Member
Author
|
@codex review |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add an explicit receive-shutdown state to TCP sockets so users of the stack can model Linux/BSD close(2) orphan semantics.
When the local receive half has been shut down and the socket is in FIN-WAIT-1 or FIN-WAIT-2, any peer payload that advances the receive sequence space now closes the socket and emits an active RST instead of being queued or answered with zero-window ACKs.
Also add a focused regression test for FIN-WAIT receive-shutdown data.