Skip to content

Fix process_vm_* syscall names in seccomp#7755

Merged
AkihiroSuda merged 1 commit intocontainerd:mainfrom
cji:patch-1
Dec 5, 2022
Merged

Fix process_vm_* syscall names in seccomp#7755
AkihiroSuda merged 1 commit intocontainerd:mainfrom
cji:patch-1

Conversation

@cji
Copy link
Copy Markdown
Contributor

@cji cji commented Dec 2, 2022

In #7693 we added two ptrace related syscalls for kernels >= 4.8, however I believe the syscall names had a minor typo.

Both the man page and the docker seccomp default that was being compared show the syscalls are named:

process_vm_readv
process_vm_writev

(This is also the syscall name we use later in this file when CAP_SYS_PTRACE is checked here)

It may be worth trying to confirm (using a toy program that uses the process_vm_ready syscall) that this now provides the expected behavior if someone can help with that.

Signed-off-by: Craig Ingram [email protected]

@k8s-ci-robot
Copy link
Copy Markdown

Hi @cji. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@samuelkarp
Copy link
Copy Markdown
Member

/ok-to-test

@AkihiroSuda AkihiroSuda merged commit be4a0d1 into containerd:main Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants