fix: report exec event from syscall exit instead of syscall entry - #29
Merged
Conversation
edeNFed
approved these changes
Aug 4, 2025
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
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.
Durrng testing and reducing the duration filter to zero, observed that processes can have the
/procfiles in an unstable state - probably not ready yet.This lead to logs liks:
The
cmdlineand the exe link seems inconsistent. In addition theenvironfiles does not contain the expected env vars - which leads to the filtering of the event.Adding an exit tracepoint to the
ecevesyscall and reporting to user space from there solves that behavior.In addition, the
duration_filterwill be used as a passthrough filter if the duration passed is zero.emergency-ticket id: EMR-5