-
Notifications
You must be signed in to change notification settings - Fork 444
helpers/btfinfo: renamed to osinfo and improved, syncing #981
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
Conversation
Can we remove the UnameRelease() and KernelIsAtLeast() functions from tracee.go after the libbpfgo PR is merged? |
This will only work after aquasecurity/libbpfgo#70 is reviewed and merged AND we bump libbpfgo dependency to that commit. Tests at: aquasecurity/libbpfgo#61 (comment) |
This comment has been minimized.
This comment has been minimized.
All tests are good but now I'm failing if no kconfig file exists from tracee side (because I need the CONFIG_ARCH_HAS_SYSCALL_WRAPPER value). I'll have to define as TRUE or FALSE by default if no kconfig file is found @yanivagman. Is that ok ? This way we can fully get rid of kconfig if there is none provided AND none in the OS. |
Use helpers/kernel_config custom KernelConfigOption's feature in order to extend KernelConfig default values and seek for specific ones needed to feed tracee-ebpf's kconfig map. Fixes: aquasecurity/libbpfgo#61
regular call
regular external files:
no os-release file, try to continue:
No os-release NOR kconfig files. Tracee assumes CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y.
Check if given kconfig in environment with no kconfig is good for libbpf:
If we manually remove CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y from the given kconfig file, for testing purposes, we have to break the arguments:
And if I put it back on (=y):
Everything seems to be working as expected. |
Signed-off-by: grantseltzer <grantseltzer@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
It was done by me accidentally when I upgradded the libbfgo dependency. I
deleted go.mod first when debugging. Not necessary for the release but yes,
it's already reverted.
…On Fri, Sep 3, 2021 at 9:25 PM Rafael David Tinoco ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In tracee-ebpf/go.mod
<#981 (comment)>:
> @@ -2,15 +2,13 @@ module github.com/aquasecurity/tracee/tracee-ebpf
go 1.16
-replace github.com/aquasecurity/tracee/tracee-ebpf/external => ./external/
-
This was done automatically by GoLand, I'll check why that happened. I see
it was already put back.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#981 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACS2XBPQUBGOOUMHTHCCS3TUAFYSNANCNFSM5DG57RMA>
.
|
FTR, I've got some minor continuation of this at: #999 |
Reference: aquasecurity/libbpfgo#60
Needs aquasecurity/libbpfgo#67 merged first.