-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8324648: Avoid NoSuchMethodError when instantiating NativePRNG #17560
Conversation
👋 Welcome back ogillespie! A progress list of the required criteria for merging this PR into |
@olivergillespie 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
|
I see that the existing caller code has a check for |
From lookup code:
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.
Seems like a good workaround. Attn @valeriepeng ;)
/reviewers 2
@olivergillespie 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 192 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev, @wangweij, @valeriepeng) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
For NativePRNG, should the dummy constructor just ignores the parameters? If passed with a non-null parameter, should it accept it? Max and Brad is more familiar with SecureRandom than me, so it's better that they chime in on this. @bradfordwetmore @wangweij |
I think Valerie is correct. Otherwise, |
Good point, thanks, I should have thought of that. I see DBRG has this for when the params are not appropriate:
I'll add something similar in my dummy constructors, unless someone objects. |
The more I think about it, adding a new public constructor seems a bit ugly and potentially confusing. So I'll offer a few more ideas. Which do you think is best?
|
No matter if we touch the |
Thanks. Updated with option 1 and removed old constructors. |
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.
Looks good to me.
Please update the copyright year. Thanks.
@@ -203,11 +203,14 @@ static boolean isAvailable() { | |||
} | |||
|
|||
// constructor, called by the JCA framework | |||
public NativePRNG() { | |||
public NativePRNG(SecureRandomParameters params) { | |||
super(); |
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.
nit: maybe super() not needed? Same goes for the Blocking and NonBlocking ctors.
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.
It was already there before, but yes it doesn't do anything useful. The other impls I've checked don't use it, so I'll remove.
/integrate Thanks for the reviews, all! |
@olivergillespie |
/sponsor |
Going to push as commit 69b2674.
Your commit was automatically rebased without conflicts. |
@wangweij @olivergillespie Pushed as commit 69b2674. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk17u |
@olivergillespie Could not automatically backport
Please fetch the appropriate branch/commit and manually resolve these conflicts by using the following commands in your personal fork of openjdk/jdk17u. Note: these commands are just some suggestions and you can use other equivalent commands you know.
Once you have resolved the conflicts as explained above continue with creating a pull request towards the openjdk/jdk17u with the title Below you can find a suggestion for the pull request body:
|
/backport jdk21u-dev |
@olivergillespie the backport was successfully created on the branch backport-olivergillespie-69b2674c in my personal fork of openjdk/jdk21u-dev. To create a pull request with this backport targeting openjdk/jdk21u-dev: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/jdk21u-dev:
|
/backport jdk22u |
@olivergillespie the backport was successfully created on the branch backport-olivergillespie-69b2674c in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u: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/jdk22u:
|
A typical call to
new SecureRandom()
is slowed down by looking for a constructor in NativePRNG which takesjava.security.SecureRandomParameters
. NativePRNG does not have such a constructor, so the search fails here, incurring all the cost of the lookup and creating a subsequent exception.Creating a dummy constructor which takes and ignores this parameter will speed up
new SecureRandom()
calls significantly.The benchmark from #17559 shows around 80% reduction in time taken to create a new SecureRandom with NativePRNG (default on my machine).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17560/head:pull/17560
$ git checkout pull/17560
Update a local copy of the PR:
$ git checkout pull/17560
$ git pull https://git.openjdk.org/jdk.git pull/17560/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17560
View PR using the GUI difftool:
$ git pr show -t 17560
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17560.diff
Webrev
Link to Webrev Comment