fix: TCP socket miss activation after close #1085
Merged
Conversation
This file contains 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
Samuka007
force-pushed
the
feat-network-rebuild
branch
from
f7e770d to
d82b5bb
Compare
smallcjy
approved these changes
Jan 12, 2025
Samuka007
merged commit c33082c
into
DragonOS-Community:feat-network-rebuild
6 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The miss activation after close of TCP cause system panic at network interupt arrive, though which should be ignored.
Now the behavior still kind of weird, the first query to the virtio "reset" after a short period of time, but the following query after the first one is immediate reset. Also, the default "reset" behavior seems not the correct behavior when you access a "non exist" server. Need further investegation.
The UDP socket seems not correctly closed.
TCP socket still couldn't connect a remote socket.
The test case "test-backlog" with actix-web runtime is still unable to run.