Skip to content

Conversation

@dougxc
Copy link
Member

@dougxc dougxc commented Jul 16, 2025

This PR fixes HotSpotJVMCIRuntime.getMirror(ResolvedJavaMethod method) and HotSpotJVMCIRuntime.getMirror(ResolvedJavaField field) so that they return null for <clinit> and an injected field respectively instead of crashing.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8362306: HotSpotJVMCIRuntime.getMirror can crash (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26346/head:pull/26346
$ git checkout pull/26346

Update a local copy of the PR:
$ git checkout pull/26346
$ git pull https://git.openjdk.org/jdk.git pull/26346/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26346

View PR using the GUI difftool:
$ git pr show -t 26346

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26346.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 16, 2025

👋 Welcome back dnsimon! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jul 16, 2025

@dougxc This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8362306: HotSpotJVMCIRuntime.getMirror can crash

Reviewed-by: gdub, never, cslucas

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 45 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Jul 16, 2025

@dougxc The following labels will be automatically applied to this pull request:

  • graal
  • hotspot

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added graal graal-dev@openjdk.org hotspot hotspot-dev@openjdk.org labels Jul 16, 2025
@dougxc dougxc marked this pull request as ready for review July 16, 2025 08:40
@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 16, 2025
@mlbridge
Copy link

mlbridge bot commented Jul 16, 2025

Webrevs

@openjdk
Copy link

openjdk bot commented Jul 16, 2025

@dougxc Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

return iklass;
}

C2V_VMENTRY_NULL(jobject, asReflectionField, (JNIEnv* env, jobject, ARGUMENT_PAIR(klass), jint index))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is the same pattern in getEncodedFieldAnnotationData, we should probably defend there as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point: c2c41aa

CompilerThreadCanCallJava canCallJava(thread, true); // Requires Java support
InstanceKlass* holder = InstanceKlass::cast(UNPACK_PAIR(Klass, klass));
return get_encoded_annotation_data(holder, holder->class_annotations(), true, filter_length, filter_klass_pointers, THREAD, JVMCIENV);
return get_encoded_annotation_data(holder, holder->class_annotations(), true, filter_length, filter_klass_pointers, THREAD, JVMCI_CHECK_NULL);
Copy link
Member

@gilles-duboscq gilles-duboscq Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can JVMCI_CHECK_ be used in return statements? i think the "check and return default value" part would be unreachable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed - I've been bitten by this before! In this case, it's harmless given that the return statement is anyway the last statement in the method. Still, I'll revert my "fix".
I'm also wondering (again?) why the C++ compiler does not warning about unreachable code.

@gilles-duboscq
Copy link
Member

Maybe you could add a test in TestResolvedJavaType.getClassInitializer to check that getMirror doesn't crash on that and returns null?

@dougxc
Copy link
Member Author

dougxc commented Jul 16, 2025

Maybe you could add a test in TestResolvedJavaType.getClassInitializer to check that getMirror doesn't crash on that and returns null?

Done: fd44d95

Copy link
Contributor

@JohnTortugo JohnTortugo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

requireInHotSpot("asReflectionField", JVMCI_CHECK_NULL);
Klass* klass = UNPACK_PAIR(Klass, klass);
InstanceKlass* iklass = check_field(klass, index, JVMCIENV);
InstanceKlass* iklass = check_field(klass, index, JVMCI_CHECK_NULL);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's another copy of this idiom in getDeclaredFieldsInfo which might be worth fixing.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 17, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jul 17, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 17, 2025
@dougxc
Copy link
Member Author

dougxc commented Jul 17, 2025

Thanks for the reviews.

/integrate

@openjdk
Copy link

openjdk bot commented Jul 17, 2025

Going to push as commit 2b11a28.
Since your change was applied there have been 45 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 17, 2025
@openjdk openjdk bot closed this Jul 17, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jul 17, 2025
@openjdk
Copy link

openjdk bot commented Jul 17, 2025

@dougxc Pushed as commit 2b11a28.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

graal graal-dev@openjdk.org hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

4 participants