Fix FFM downcall exception stack frame handling - #24660
Open
babsingh wants to merge 1 commit into
Open
Conversation
When an exception is pending after an FFM downcall, avoid executing the normal JNI return path. That path removes the special stack frame before exception dispatch, leaving the VM to walk an invalid frame and potentially crash. For allocation failures before the native invocation, construct an internal native stack frame before raising the native OutOfMemoryError so the stack remains walkable during exception dispatch. Related: eclipse-openj9#24654 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
Contributor
Author
|
jenkins test sanity plinux jdk27 |
Contributor
Author
|
jenkins test sanity amac jdk21 |
This was referenced Aug 28, 2026
tajila
reviewed
Aug 28, 2026
Contributor
|
jenkins test sanity,extended.functional zlinux jdk27,jdk25 |
Contributor
Author
|
50x Only a known, unrelated failure is seen in the PR builds: |
babsingh
marked this pull request as ready for review
August 28, 2026 23:44
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 an exception is pending after an FFM downcall, avoid executing
the normal JNI return path. That path removes the special stack frame
before exception dispatch, leaving the VM to walk an invalid frame
and potentially crash.
For allocation failures before the native invocation, construct an
internal native stack frame before raising the native
OutOfMemoryErrorso the stack remains walkable during exception dispatch.
Related: #24654