-
Notifications
You must be signed in to change notification settings - Fork 3.8k
seccomp: seccomp: add syscalls related to PKU in default policy #7163
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
Conversation
Add pkey_alloc(2), pkey_free(2) and pkey_mprotect(2) in seccomp default profile. pkey_alloc(2), pkey_free(2) and pkey_mprotect(2) can only configure the calling process's own memory, so they are existing "safe for everyone" syscalls. Signed-off-by: Sebastiaan van Stijn <[email protected]>
|
@samuelkarp @AkihiroSuda PTAL |
That one's related to clock_settime64. Looks like you meant to reference moby/moby#43490? |
|
Ah, derp. Yes, had both open in a tab, and copied the wrong one |
estesp
left a comment
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.
LGTM
mikebrow
left a comment
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.
|
could someone kick CI on this one? |
|
Done |
|
"Machine type with name 'c2-standard-2' does not exist in zone 'us-central1-c'." |
|
/test ? |
|
@mikebrow: The following commands are available to trigger required jobs:
Use
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test pull-containerd-sandboxed-node-e2e |
hmm |
same as moby/moby#43490
Add pkey_alloc(2), pkey_free(2) and pkey_mprotect(2) in seccomp default profile.
pkey_alloc(2), pkey_free(2) and pkey_mprotect(2) can only configure
the calling process's own memory, so they are existing "safe for everyone" syscalls.