-
Notifications
You must be signed in to change notification settings - Fork 124
Add SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV #1201
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
Add SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV #1201
Conversation
Hi @alban. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
/ok-to-test
Thank you!
type Arch string | ||
|
||
// +kubebuilder:validation:Enum=SECCOMP_FILTER_FLAG_TSYNC;SECCOMP_FILTER_FLAG_LOG;SECCOMP_FILTER_FLAG_SPEC_ALLOW | ||
// +kubebuilder:validation:Enum=SECCOMP_FILTER_FLAG_TSYNC;SECCOMP_FILTER_FLAG_LOG;SECCOMP_FILTER_FLAG_SPEC_ALLOW;SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV |
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.
// +kubebuilder:validation:Enum=SECCOMP_FILTER_FLAG_TSYNC;SECCOMP_FILTER_FLAG_LOG;SECCOMP_FILTER_FLAG_SPEC_ALLOW;SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV | |
//nolint:lll // required for kubebuilder | |
// +kubebuilder:validation:Enum=SECCOMP_FILTER_FLAG_TSYNC;SECCOMP_FILTER_FLAG_LOG;SECCOMP_FILTER_FLAG_SPEC_ALLOW;SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV |
722c7dd
to
8407ce0
Compare
Linux 5.19 introduced a new seccomp flag: SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=c2aa2dfef243 It is useful for seccomp notify when handling notification from Golang programs which are often preempted by the runtime with SIGURG. The flag was added in runtime-spec: opencontainers/runtime-spec@4bcd065 and implemented in crun: containers/crun@396ac88 But not yet in runc. Signed-off-by: Alban Crequy <albancrequy@microsoft.com>
8407ce0
to
96449e9
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alban, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
Linux 5.19 introduced a new seccomp flag:
SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=c2aa2dfef243
It is useful for seccomp notify when handling notification from Golang programs which are often preempted by the runtime with SIGURG.
Which issue(s) this PR fixes:
None
Does this PR have test?
N/A
Special notes for your reviewer:
The flag was added in runtime-spec:
opencontainers/runtime-spec@4bcd065
and implemented in crun:
containers/crun@396ac88
But not yet in runc. We need seccomp/libseccomp#387 first.
Does this PR introduce a user-facing change?
cc @rata