Split iovec reading for tcp_recvmsg #1108
Merged
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 is a regression fix for a refactor we did in the last 2 months to read multiple segments of the iov pointer inside msghdr. In case of a large incoming request, the kernel buffer used for iov might be replenished and we'll loose the pointer to the original buffer, if we read the iov address at probe return.
After the nice refactor of the code by @rafaelroquetto, it was easy to separate the acquisition of the iov pointer from the reading of the data. I had to duplicate the data structure for the purpose of keeping the iov pointers, since we can't use pointers in eBPF maps value structs.