-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8361447: [REDO] Checked version of JNI Release<type>ArrayElements needs to filter out known wrapped arrays #26177
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
Conversation
…ds to filter out known wrapped arrays
/contributor add @tstuefe |
👋 Welcome back dholmes! A progress list of the required criteria for merging this PR into |
@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 43 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 |
@dholmes-ora |
@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. |
@MBaesken please run this through your testing - thanks. |
Webrevs
|
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 to me. Thank you for considering my suggestions.
Thanks for the review @tstuefe ! |
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 think this looks good. Let's see what the tests and UBSan say (Matthias is testing).
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. is_readable_range avoids unaligned SafeFetch32, right?
Right. It aligns down to |
It also avoids the endian-ness issue of reading a byte from a 32-bit int. Thanks for the review @coleenp ! |
Hi David, the tests look good, I did not see issues related to your change ! |
Thanks for doing the testing @MBaesken ! Thanks for the review @TheRealMDoerr ! /integrate |
Going to push as commit f67e435.
Your commit was automatically rebased without conflicts. |
@dholmes-ora Pushed as commit f67e435. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk jdk25 |
@dholmes-ora the backport was successfully created on the branch backport-dholmes-ora-f67e4354-jdk25 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk25, 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/jdk:
|
The original PR (#26123) had incorrect usage of
SafeFetch32
. This PR replaces that with the use ofos::is_readable_range
as proposed by @tstuefe (thank you!). In addition I found that code was no longer getting exercised by the regression test so I added a gtest for that (during which it was discovered that the new implementation inverify
requires any gtest that uses it to beTEST_VM
rather thanTEST
).Testing: tiers 1-4
Thanks
Progress
Issue
Reviewers
Contributors
<[email protected]>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26177/head:pull/26177
$ git checkout pull/26177
Update a local copy of the PR:
$ git checkout pull/26177
$ git pull https://git.openjdk.org/jdk.git pull/26177/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26177
View PR using the GUI difftool:
$ git pr show -t 26177
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26177.diff
Using Webrev
Link to Webrev Comment