[1.0] libct/seccomp: skip redundant rules #3129
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes using runc with podman on my system (Fedora 34).
> $ podman --runtime `pwd`/runc run --rm --memory 4M fedora echo it works
> Error: unable to start container process: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied
The problem is, libseccomp returns EPERM when a redundant rule (i.e. the
rule with the same action as the default one) is added, and podman (on
my machine) sets the following rules in config.json:
<....>
"seccomp": {
"defaultAction": "SCMP_ACT_ERRNO",
"architectures": [
"SCMP_ARCH_X86_64",
"SCMP_ARCH_X86",
"SCMP_ARCH_X32"
],
"syscalls": [
{
"names": [
"bdflush",
"io_pgetevents",
<....>
],
"action": "SCMP_ACT_ERRNO",
"errnoRet": 1
},
<....>
(Note that defaultErrnoRet is not set, but it defaults to 1).
With this commit, it works:
> $ podman --runtime `pwd`/runc run --memory 4M fedora echo it works
> it works
Add an integration test (that fails without the fix).
Similar crun commit:
* containers/crun@08229f3fb904c5ea19a7d9
Signed-off-by: Kir Kolyshkin <[email protected]>
Cherry picked from commit 5dd92fd.
Minor conflict in libcontainer/seccomp/seccomp_linux.go due to
missing commit e44bee1.
Signed-off-by: Kir Kolyshkin <[email protected]>
kolyshkin
added
area/seccomp
kind/bug
backport/1.0-pr
Contributor
Author
|
I'm sure Fedora users will appreciate it. |
AkihiroSuda
approved these changes
Aug 10, 2021
mrunalp
approved these changes
Aug 11, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #3109 (partial -- last commit only) to release-1.0 branch. Original description follows.
This fixes using runc with podman on my system (Fedora 34).
The problem is, libseccomp returns EPERM when a redundant rule (i.e. the
rule with the same action as the default one) is added, and podman (on
my machine) sets the following rules in config.json:
(Note that defaultErrnoRet is not set, but it defaults to 1).
With this commit, it works:
Add an integration test (that fails without the fix).
Similar crun commit:
Signed-off-by: Kir Kolyshkin [email protected]
Cherry picked from commit 5dd92fd.
Minor conflict in libcontainer/seccomp/seccomp_linux.go due to
missing commit e44bee1.
Signed-off-by: Kir Kolyshkin [email protected]