| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082784 | emb-9 | David Holmes | P3 | Resolved | Fixed | team |
| JDK-8086501 | 8u65 | David Holmes | P3 | Resolved | Fixed | b01 |
| JDK-8079114 | 8u60 | David Holmes | P3 | Resolved | Fixed | b14 |
| JDK-8137566 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b01 |
| JDK-8079949 | emb-8u60 | David Holmes | P3 | Resolved | Fixed | team |
For historical reasons, dating back to LinuxThreads, os::fork_and_exec uses direct syscalls to perform fork and execve functions. The fork syscall has been deprecated on linux for quite some time and some distributions are now shipping with deprecated syscalls removed - this results in a ENOSYS error and the "OnError" commands that utilize os::fork_and_exec no longer work.
The problem was discussed here:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-April/017916.html
It seems the concerns surrounding direct use of glibc fork() and exec() are no longer legitimate and Martin Buchholz reports that Google replaced the syscalls with glibc call some time ago and have not had any problems. So we propose to apply the same change uniformly on Linux.
The problem was discussed here:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-April/017916.html
It seems the concerns surrounding direct use of glibc fork() and exec() are no longer legitimate and Martin Buchholz reports that Google replaced the syscalls with glibc call some time ago and have not had any problems. So we propose to apply the same change uniformly on Linux.
- backported by
-
JDK-8079114 [Linux] Replace syscall use in os::fork_and_exec with glibc fork() and execve()
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-