[Parse incomplete chunks 9/9] Add bpf test for loop limit exceeded #1794
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
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.
Summary: Adds a bpf test for HTTP that triggers the gap condition
LoopLimitExceededbased on a NodeJS application submitted in community slack. It submits an iovec with 257 elements, which is greater than our loop limit of 42. Our current behavior is that we merge 41 events into the data stream buffer, getting us to 878 bytes. Then on 42nd iov we reach loop limit, record the gap in metadata, and pad the rest with filler (or leave a gap if lazy parsing is enabled).Type of change: /kind feature
Test Plan: Tested for both lazy and non-lazy HTTP parsing. Checked that metrics consistently show the loop limit exceeded condition for an iovec with length 257.