Add eBPF plugin to trace execve system calls #126
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
Noticed that after the module is closed the tracepoint continues to appear in |
This plugin uses eBPF and has less performance overhead than using the audit subsystem to capture execve system calls. Also it does not drop events under heavy load conditions. It requires linux 5.8+ for eBPF ringbuffer support - artifacts should check that before calling it. It uses tracepoint/sched/sched_process_exec because tracepoint/syscalls/sys_enter_execve is not reliable bpftrace/bpftrace#2523 (comment)
The execsnoop plugin can be used if it's in the binary and the kernel is 5.8+ required for eBPF ringbuffer support. Otherwise the audit plugin will be used as before.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using eBPF to trace execve system calls is more efficient than using the audit subsystem, so systems with high exec workloads should see less overall performance degradation. The new plugin requires kernel 5.8+ and systems without this will continue to use the audit plugin.