Fix dropped netlink messages when too many for the buffer #1
Conversation
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
Because the buffer size is a fixed 4kb, if a netlink message is truncated, only some parts of it would end up in the buffer, leading to the message being dropped. Instead, peek at the message size ahead via MSG_PEEK|MSG_TRUNC and allocate a buffer to fit it dynamically. (AFAIK netlink messages can be >4kb anyway, so this is a bit more generally useful.)
|
lgtm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Because the buffer size is a fixed 4kb, if a netlink message is truncated, only some parts of it would end up in the buffer, leading to the message being dropped. Instead, peek at the message size ahead via MSG_PEEK|MSG_TRUNC and allocate a buffer to fit it dynamically. (AFAIK netlink messages can be >4kb anyway, so this is a bit more generally useful.)