fix(seccomp): extend default whitelist and merge ALLOWED_SYSCALLS - #275
Merged
fatelei merged 5 commits intoJul 1, 2026
Merged
Conversation
Contributor
Author
|
Verified locally: go test ./internal/core/lib/... — pass. |
Contributor
Author
|
Hey, this PR is ready for review when you have a chance. Happy to adjust if anything needs changing. |
fatelei
approved these changes
Jul 1, 2026
6 tasks
6 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #274
Related: langgenius/dify#38105
Problem
Code execution nodes intermittently fail with
operation not permittedwhen modern glibc/CPython hits syscalls missing from the default seccomp whitelist (e.g. sched_getaffinity, statx, pipe2).Setting ALLOWED_SYSCALLS also replaced the entire default whitelist instead of extending it, so the common workaround could break basic I/O syscalls.
Changes
Verification