P4 | Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2176831 | 7 | Kumar Srinivasan | P3 | Closed | Fixed | b07 |
| JDK-2171848 | 6u4 | Kumar Srinivasan | P3 | Closed | Fixed | b03 |
We should protect the VM by making the addr 0x0 non-writeable by creating
a Read-only page mapped
at address 0x0, this will prevent (very hard to find) Bugs.
There are two case this can happen:
1) An OS bug which decides to map over the 0x0 and make it legal
see Bug: 6374692
2) User code preceding CreateJavaVM may do something like this
mmap(0, MAP_FIXED). The OS could map 0x0, and this very be allowed,
as mmap(2) spec. is not very clear, whether it is legal or not.
a Read-only page mapped
at address 0x0, this will prevent (very hard to find) Bugs.
There are two case this can happen:
1) An OS bug which decides to map over the 0x0 and make it legal
see Bug: 6374692
2) User code preceding CreateJavaVM may do something like this
mmap(0, MAP_FIXED). The OS could map 0x0, and this very be allowed,
as mmap(2) spec. is not very clear, whether it is legal or not.
- backported by
-
JDK-2171848 -Xcheck:jni Protect the system stack with a NULL page
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6468054 Solaris x86 : JVM Crash in JNDI API
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-