-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Rename seccompiler binary, deprecate --basic parameter and add extra thread name validation #2628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename seccompiler binary, deprecate --basic parameter and add extra thread name validation #2628
Conversation
Once we upstream the seccompiler library to rust-vmm and use it from there, the seccompiler binary in Firecracker will need a different name, so that it doesn't create confusion. As such, we rename the seccompiler binary to seccompiler-bin now, so that we don't rename it later, avoiding a breaking change in naming. The seccompiler library keeps its name and it will be used, under the hood by the binary as well. Signed-off-by: alindima <[email protected]>
docs/seccompiler.md
Outdated
interface, with a couple of helper functions, for deserializing and installing | ||
the binary filters. | ||
Besides the seccompiler-bin executable, seccompiler also exports a small | ||
library interface, with a couple of helper functions, for deserializing and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seccompiler also exports a library interface, with helper functions for deserializing......
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: alindima <[email protected]>
Signed-off-by: alindima <[email protected]>
Signed-off-by: alindima <[email protected]>
The --basic parameter is only used to support Firecracker's deprecated --seccomp-level argument. It makes sense to deprecate it and remove it once --seccomp-level is removed from Firecracker. Signed-off-by: alindima <[email protected]>
Signed-off-by: alindima <[email protected]>
7cdf03b
to
ba6d19e
Compare
@serban300 @AlexandruCihodaru I addressed the nits, PTAL |
Reason for This PR
Considering the proposal of upstreaming the seccompiler library to rust-vmm,
the seccompiler binary used by Firecracker will need a slightly different name, so that
it doesn't clash with the library name.
Also, since the only use of the
--basic
flag of seccompiler-bin is to support Firecracker's--seccomp-level 1
, which is deprecated, we are also deprecating the--basic
flag.Duplicated thread names in the JSON filter were allowed, due to the fact that the JSON spec doesn't forbid this. For the seccomp use case, however, it can result in undefined behaviour.
Description of Changes
rename the seccompiler binary to seccompiler-bin
deprecate the seccompiler-bin
--basic
flag. It now displays a runtime warning when used.add a custom deserializer for the Json file that errors if there are duplicate thread keys in the file. also added a regression test.
This functionality can be added in
rust-vmm
.License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]
git commit -s
).unsafe
code is properly documented.firecracker/swagger.yaml
.CHANGELOG.md
.