Handle ENOBUFS correctly in socketio_berkeley #590
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
This issue was first reported on Green Hill's embedded Linux, where the number of telemetry messages was big enough to fill in the output buffers of the OS and cause send() to return error and set errno to ENOBUFS. ENOBUFS should be treated as a transient error, not critical as it was so far.
danewalton-msft
approved these changes
Apr 13, 2022
ericwolz
approved these changes
Apr 13, 2022
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.
This issue was first reported on Green Hill's embedded Linux,
where the number of telemetry messages was big enough to
fill in the output buffers of the OS and cause send() to return
error and set errno to ENOBUFS.
ENOBUFS should be treated as a transient error, not critical as
it was so far.