chore(userspace/falco): always print invalid syscalls from custom set #2578
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.
Co-authored-by: Roberto Scolaro roberto.scolaro21@gmail.com
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
When we insert only one bad entry in the
base_syscall.custom_set
sequence (or a sequence of bad entries), Falco fails to output the "invalid syscalls" warning because it sees the custom set as empty, given that it crops the invalid values. This PR makes sure that the warning is always printed.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: