Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: call bpf_object__open_mem from go #314

Closed
wants to merge 1 commit into from

Conversation

geyslan
Copy link
Member

@geyslan geyslan commented Apr 3, 2023

This changes libbpfgo to call bpf_object__open_mem directly from go instead of doing this via a C wrapper. What this means is that we maintained opts creation in C, but the actual libbpf object open call is done in go.

This creates two new functions in libbpfgo.h as helpers:

  • bpf_object_open_opts_new()
  • bpf_object_open_opts_free()

Context: #304

Additionally, this commit enforces the use of defer and resolves a potential CKconfigPath leak when len(args.KConfigFilePath) is > 2.

This changes libbpfgo to call bpf_object__open_mem directly from go
instead of doing this via a C wrapper. What this means is that we
maintained opts creation in C, but the actual libbpf object open call
is done in go.

This creates two new functions in libbpfgo.h as helpers:
- bpf_object_open_opts_new()
- bpf_object_open_opts_free()

Context: aquasecurity#304

Additionally, this commit enforces the use of defer and resolves a
potential CKconfigPath leak when len(args.KConfigFilePath) is > 2.
@geyslan geyslan added the chore label Apr 3, 2023
@geyslan geyslan requested a review from rafaeldtinoco April 3, 2023 12:34
@geyslan geyslan self-assigned this Apr 3, 2023
@rafaeldtinoco
Copy link
Contributor

rebased at: #325 (keeping credits).

@geyslan geyslan deleted the api-call-from-go branch May 29, 2023 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants