Skip to content

Block all signals in the parent before fork - #51

Merged
guillerodriguez merged 1 commit into
masterfrom
feat/exec-block-signals-around-fork
Aug 4, 2026
Merged

Block all signals in the parent before fork#51
guillerodriguez merged 1 commit into
masterfrom
feat/exec-block-signals-around-fork

Conversation

@guillerodriguez

Copy link
Copy Markdown
Contributor

Block all signals on the spawning thread before fork, so that the child process setup (descriptor wiring, close-on-exec sweep, chdir) cannot be interrupted by signals (so no call can fail with EINTR).

This is hardening: previously, the child's setup was safe only as long as neither the VM nor native code loaded into the process installed disruptive signal handlers. Blocking makes the setup safe by construction.

Block all signals on the spawning thread before fork, so that the
child process setup (descriptor wiring, close-on-exec sweep, chdir)
cannot be interrupted by signals (so no call can fail with EINTR).

This is hardening: previously, the child's setup was safe only
as long as neither the VM nor native code loaded into the process
installed disruptive signal handlers. Blocking makes the setup
safe by construction.
@guillerodriguez
guillerodriguez requested a review from phvega August 3, 2026 10:18
@guillerodriguez
guillerodriguez merged commit cdb0b69 into master Aug 4, 2026
2 of 3 checks passed
@guillerodriguez
guillerodriguez deleted the feat/exec-block-signals-around-fork branch August 4, 2026 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants