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 #325

Merged
merged 1 commit into from
May 3, 2023
Merged

chore: call bpf_object__open_mem from go #325

merged 1 commit into from
May 3, 2023

Conversation

rafaeldtinoco
Copy link
Contributor

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: #304

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

This is a rebase to #314 (which I'm +1)

@rafaeldtinoco rafaeldtinoco requested a review from geyslan May 3, 2023 01:36
@rafaeldtinoco rafaeldtinoco merged commit 0238ec3 into aquasecurity:main May 3, 2023
@rafaeldtinoco rafaeldtinoco deleted the api-call-from-go branch May 3, 2023 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants