Drop syscall enter event parsing #55
Merged
+138
−526
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
bleggett
force-pushed
the
bleggett/fix-extract
branch
from
be7a520 to
55069cc
Compare
azenla
approved these changes
Feb 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the latest release of Falco (0.43), the eBPF syscall hooks were refactored to only hook syscall exit events, thereby avoiding some of the gross state machine stuff where the code previously needed to watch for enter AND exit events for the same thread and do cross-correlation/enrichment from both.
Mirror that here, as that's considerably less gross and simplifies our logic as well.
Note that this changes means all
latencyfields, which previously measured latency between syscall enter and exit, now are no-ops that return 0. This is also the current Falco default formodern_bpf.