fix: allow python fd3 reads under seccomp#251
Merged
Conversation
Permit the descriptor metadata syscalls used by the Python FD 3 bootstrap after sandbox setup so simple code execution no longer crashes with a bad system call.
fatelei
approved these changes
Apr 21, 2026
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.
Summary
Why
The Python FD 3 bootstrap introduced a regression where simple code execution could terminate with
signal: bad system callafter seccomp was enabled. This change restores normal execution by permitting the file descriptor operations the bootstrap now relies on.Closes #250
This PR is drafted by
gpt-5.4(high)and I'm responsible for all the changes. I have reviewed the code and varified the behavior, while breaks may still exist. Reach me to fix in this case.Testing
go test -exec /bin/true ./internal/static/python_syscall