Fix stack usage validation for eBPF local functions #566
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.
Stack usage for eBPF local functions was incorrectly calculated whether or not a custom stack usage calculator was present or not. This PR fixes that issue.
In addition to fixing that bug, this PR also changes the default eBPF program stack size and the default stack size for local functions in eBPF programs (8K and 256 bytes, respectively).
This PR also adds support for a stack usage calculator that does not want to allow an eBPF program's local functions to use any stack space at all.