-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8323243: JNI invocation of an abstract instance method corrupts the stack #17337
Conversation
👋 Welcome back dholmes! A progress list of the required criteria for merging this PR into |
@dholmes-ora The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
/label add hotspot-runtime |
@dholmes-ora |
@dholmes-ora |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a couple of minor comments but looks good.
test/hotspot/jtreg/runtime/jni/abstractMethod/AbstractMethod.jasm
Outdated
Show resolved
Hide resolved
test/hotspot/jtreg/runtime/jni/abstractMethod/TestJNIAbstractMethod.java
Outdated
Show resolved
Hide resolved
@dholmes-ora 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:
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 78 new commits pushed to the
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch. Looks good, with minor test suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good.
Minor nit still: I think we gotta try the Java side first, because that checks the expected behavior. Right now, if JNI fails, we don't really know if that is a product bug (= "JNI failed to throw AME when it should"), or a test bug (= "the way the test is written, even plain Java does not throw AME"). The point of positive test is to verify the test does what it should: if Java test passes and JNI fails, there is a clear indication JNI does something wrong.
Can we also say "Did not get AbstractMethodError from JNI!" and "Did not get AbstractMethodError from Java!" in exception messages, so that it would be abundantly clear which test had failed.
@shipilev Test updated as suggested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent, good to go!
Thanks @shipilev ! /integrate |
/backport jdk22 |
Going to push as commit 71d9a83.
Your commit was automatically rebased without conflicts. |
@dholmes-ora Pushed as commit 71d9a83. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@dholmes-ora the backport was successfully created on the branch backport-dholmes-ora-71d9a83d in my personal fork of openjdk/jdk22. To create a pull request with this backport targeting openjdk/jdk22:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22:
|
See JBS for details.
TL;DR - if an instance method is abstract then JNI front-end should throw AbstractMethodError.
Testing:
Thanks.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17337/head:pull/17337
$ git checkout pull/17337
Update a local copy of the PR:
$ git checkout pull/17337
$ git pull https://git.openjdk.org/jdk.git pull/17337/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17337
View PR using the GUI difftool:
$ git pr show -t 17337
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17337.diff
Webrev
Link to Webrev Comment