kubevirt/0004-seccomp-Use-Names-field-to-define-the-syscall.patch
2024-01-05 20:44:32 +00:00

28 lines
991 B
Diff

From 0564fc86b7387d2c3b9f16a5f712ed3282c894e5 Mon Sep 17 00:00:00 2001
From: Vasiliy Ulyanov <vulyanov@suse.de>
Date: Fri, 15 Dec 2023 13:22:10 +0100
Subject: [PATCH] seccomp: Use 'Names' field to define the syscall
Apparently, 'Name' has been deprecated in favour of 'Names'. Some
container runtimes do not handle 'Name' and thus fail to correctly set
the profile for seccomp.
Signed-off-by: Vasiliy Ulyanov <vulyanov@suse.de>
---
pkg/virt-handler/seccomp/seccomp.go | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pkg/virt-handler/seccomp/seccomp.go b/pkg/virt-handler/seccomp/seccomp.go
index abc20b24af9e..f2ff71ac0bcc 100644
--- a/pkg/virt-handler/seccomp/seccomp.go
+++ b/pkg/virt-handler/seccomp/seccomp.go
@@ -70,7 +70,7 @@ func defaultProfile() *seccomp.Seccomp {
}
profile.Syscalls = append(profile.Syscalls, &seccomp.Syscall{
- Name: "userfaultfd",
+ Names: []string{"userfaultfd"},
Action: seccomp.ActAllow,
Args: []*seccomp.Arg{},
})