-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
seccomp: add pidfd syscalls #41665
seccomp: add pidfd syscalls #41665
Conversation
Signed-off-by: Mark Vainomaa <mikroskeem@mikroskeem.eu>
013520e
to
e5e238b
Compare
e5e238b
to
fd41ae9
Compare
@justincormack PTAL |
Should I also create a separate PR against |
Changes to the 19.03 branch are backported / cherry-picked after a PR is merged on master. (Also wanting to wait for review, and to discuss if this change is "safe" to backport to 19.03, as docker 20.10 is imminent, and 19.03 is quite late in its support cycle). If this PR is accepted/merged, a PR should likely be opened in the containerd repository as well, to update the seccomp-profile accordingly |
Signed-off-by: Mark Vainomaa <mikroskeem@mikroskeem.eu>
fd41ae9
to
f7bcb02
Compare
- What I did
Added
pidfd_{getfd, open, send_signal}
syscalls into default seccomp profile, closes issue #41664.- How I did it
By adding syscall names into the json file.
- How to verify it
See docker/for-linux#1142 reproduction steps.
- Description for the changelog
Add support for pidfd_* syscalls into default seccomp profile. Closes #41664
- A picture of a cute animal (not mandatory but encouraged)
Maybe this Bernese Mountain Dog will do