This repository was archived by the owner on Aug 18, 2026. It is now read-only.
backend: support per-rule seccomp actions - #102
Closed
lu-zero wants to merge 1 commit into
Closed
Conversation
Allow each SeccompRule to carry an optional action that overrides the filter-level match_action when set. Add SeccompRule::new_with_action and SeccompRule::always; emit the rule's own RET in the generated BPF. Condition-less rules are valid only when they specify an action. Rules without a per-rule action keep the previous behavior (empty rule vectors and SeccompRule::new still use match_action). Cover BPF emission in unit tests and install-time behavior for always() and new_with_action() in integration tests. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
34 tasks
Member
|
@lu-zero are you still interested in getting this PR merged? If yes, could you please re-open it in https://github.com/rust-vmm/rust-vmm/. We moved seccompiler there. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allow each SeccompRule to carry an optional action that overrides the filter-level match_action when set. Add SeccompRule::new_with_action and SeccompRule::always; emit the rule's own RET in the generated BPF. Condition-less rules are valid only when they specify an action.
Rules without a per-rule action keep the previous behavior (empty rule vectors and SeccompRule::new still use match_action).
Cover BPF emission in unit tests and install-time behavior for always() and new_with_action() in integration tests.
Spun off from #99