fix some sendmsg and recvmsg issue #1030
Merged
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
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.
For the sendmsg function, the msg parameter is an input-only parameter, not an input-output parameter. The interface does not modify the user-provided msg structure, and no conversion is required after the send operation completes.
For the iovec_share2local interface, regarding functions like readv and recvmsg, the FreeBSD-side interfaces do not modify the iov_len of the iovec structures. Since we have already invoked msghdr_share_alloc, which synchronizes the variable sizes of the iovec, there is no need to offset the iov_base