Reset the child signal mask before exec - #50
Open
guillerodriguez wants to merge 1 commit into
Open
Conversation
When spawning a process via Runtime.exec() or ProcessBuilder, the executed process inherits the signal mask of the JVM thread that spawned it. The JVM's signal mask is an implementation detail of the runtime, and not part of the execution environment a child program expects. The mask must therefore be cleared when spawning child processes: otherwise, they may exhibit unexpected behaviour depending on which signals are blocked (e.g. cannot be interrupted with SIGINT, will not receive SIGPIPE when writing to a closed pipe, etc.). Fix by installing an empty signal mask in the child immediately before executing the target program. Fixes #49 (BZ#126539) Signed-off-by: Guillermo Rodríguez <grodriguez@ingelabs.com>
phvega
approved these changes
Jul 31, 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
2 participants
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.
When spawning a process via Runtime.exec() or ProcessBuilder, the executed process inherits the signal mask of the JVM thread that spawned it.
The JVM's signal mask is an implementation detail of the runtime, and not part of the execution environment a child program expects. The mask must therefore be cleared when spawning child processes: otherwise, they may exhibit unexpected behaviour depending on which signals are blocked (e.g. cannot be interrupted with SIGINT, will not receive SIGPIPE when writing to a closed pipe, etc.).
Fix by installing an empty signal mask in the child immediately before executing the target program.
Fixes #49 (BZ#126539)