Fixed bug related to lwIP TCP socket errors. When the lwIP Raw API #13
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
invokes the registerd 'tcp_err' handler, the socket is not provided for a reason. After the error handler returns, lwIP frees the TCP PCB object. If the error handler has already freed the TCP PCB in the error handler, the TCP PCB pool within lwIP is tainted and the lwIP stack will get stuck in an infinite loop.
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.
invokes the registerd 'tcp_err' handler, the socket is not
provided for a reason. After the error handler returns, lwIP frees
the TCP PCB object. If the error handler has already freed the TCP
PCB in the error handler, the TCP PCB pool within lwIP is tainted
and the lwIP stack will get stuck in an infinite loop.