fix(build): add syscall validation before creating profile #35
Conversation
This file contains 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
Signed-off-by: Alessio Greggi <ale_grey_91@hotmail.it>
ccoVeille
reviewed
Aug 13, 2024
Co-authored-by: ccoVeille <3875889+ccoVeille@users.noreply.github.com>
ccoVeille
approved these changes
Aug 14, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Fix #22
In this PR I've added a new function under the
internal/seccomputils/package to validate the syscalls before adding the to the seccomp profile.This is done because we could include even files not generated by
harpoon, so to ensure all the syscalls we are going to add to the profile are valid, there's now a function that avoid putting garbage on that.Additionally I moved the old package
internal/syscallwriter/underinternal/seccomputils/since their scopes are quite similar.