-
Notifications
You must be signed in to change notification settings - Fork 584
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
Update syscall tables and seccomp groups #5188
Comments
now covers syscalls up to including process_madvise (440) group assignment was blindly copied from systemd: https://github.com/systemd/systemd/blob/729d2df8065ac90ac606e1fff91dc2d588b2795d/src/shared/seccomp-util.c#L305 the only exception is close_range, which was added to both @basic-io and @File-system this commit adds the following syscalls to the default blacklist: pidfd_getfd,fsconfig,fsmount,fsopen,fspick,move_mount,open_tree
@smitsohu can we close? |
Closing! |
Misc: These commits seem to be related:
And I made a few WIP commits related to the first one. Since this issue appears to be the most relevant one to that commit, I renamed |
(Late review)
Please try to avoid doing both sorting and logical changes on the same commit, Considering that the tables weren't fully sorted (by syscall name), the diffs
Or like this:
|
Related: #3106
Since your last seccomp groups update Linux got new syscalls like
clone3
(@process
),close_range
(@basic-io
) ormove_mount
,open_tree
,fsconfig
,fsmount
,fsopen
,fspick
(@mount
). We should update the group definitions to include newly added syscalls.The text was updated successfully, but these errors were encountered: