JDK-8357683 : (process) SIGQUIT still blocked after JDK-8234262 with jdk.lang.Process.launchMechanism=FORK or VFORK
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 8,25,26
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux,os_x,aix
  • Submitted: 2025-05-24
  • Updated: 2025-05-30
  • Resolved: 2025-05-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25 masterFixed
Related Reports
Relates :  
JDK-8357179 - Deprecate VFORK launch mechanism from Process implementation (linux)
Relates :  
JDK-8234262 - Unmask SIGQUIT in a child process
Description
JDK-8234262 unblocks SIGQUIT for posix_spawn mode (the default), but it is still blocked for FORK and VFORK modes.

Repro case JDK-8234262 is sufficient to show this: just execute `java/lang/ProcessBuilder/UnblockSignals.java` with `-Djdk.lang.Process.launchMechanism=FORK`.

For FORK, we should also unblock the signal after the fork and before the exec.

For VFORK, we should leave it that way - VFORK will be deprecated and removed soon, and changing the signal mask would influence the parent process.
Comments
Changeset: ae3d96a4 Branch: master Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2025-05-30 13:40:25 +0000 URL: https://git.openjdk.org/jdk/commit/ae3d96a4ec87262bc2f01d87fe91daa5d0d3966f
30-05-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/25428 Date: 2025-05-24 05:49:43 +0000
24-05-2025