Fix mode of ReleasePrimitiveArrayCritical to ensure copying of data #215
Conversation
This file contains 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
keithc-ca
approved these changes
May 24, 2023
|
Jenkins compile alinux64 jdk17 |
1 similar comment
|
Jenkins compile alinux64 jdk17 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change mode value from
JNI_ABORTto0inReleasePrimitiveArrayCriticalof arrays pertaining to EC and PBE key generation.This makes no difference if a direct reference to the array is provided by the JVM, but it ensures copying of data to the original array, in case a copy of it was provided when calling
GetPrimitiveArrayCritical.Back-ported from: ibmruntimes/openj9-openjdk-jdk#603
Signed-off by: Kostas Tsiounis kostas.tsiounis@ibm.com