_initialize_ebpf_object_native: only clean up locally-created objects #2125
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.
Description
_initialize_ebpf_object_native
calls_clean_up_ebpf_object
in its failure path, which releases all resources in the object. This leads to all kinds of errors, including double frees of memory and closures of OS handles.This usage of
_clean_up_ebpf_object
is unlike the other_initialize_ebpf_object*
routines, which release only locally-created resources. Fix this misbehavior by aligning with the clean-up-what-you-created pattern.Resolves #2122
Testing
Tested in XDP stress test, plus any coverage in eBPF CI/CD.
Documentation
N/A.