8258419: RSA cipher buffer cleanup

[wangweij]

Some array allocation is not necessary, and the content can be cleaned.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8258419: RSA cipher buffer cleanup

Reviewers

• Valerie Peng (@valeriepeng - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk16 pull/26/head:pull/26
$ git checkout pull/26

[bridgekeeper]

👋 Welcome back weijun! 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]

@wangweij The following label will be automatically applied to this pull request:

• security

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.

[mlbridge]

Webrevs

• 00: Full (09c756d)

[valeriepeng]

Need a noreg-xxx label since there is no regression test.

[wangweij]

Need a noreg-xxx label since there is no regression test.

noreg-cleanup Added. Thanks.

[valeriepeng]

Looks good.

[openjdk]

@wangweij 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:

8258419: RSA cipher buffer cleanup

Reviewed-by: valeriep

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 5 new commits pushed to the master branch:

• e911351: 8258140: Update @jls tags in java.base for renamed/renumbered sections
• ce36aea: 8257822: C2 crashes with SIGFPE due to a division that floats above its zero check
• fa1cbb4: 8258404: Restore stacktrace reuse after 8258094
• 7ff9c85: 8258242: Type profile pollution occurs when memory segments of different kinds are used
• 09e8675: 8255381: com/sun/jdi/EATests.java should not suspend graal threads

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

[wangweij]

/integrate

[openjdk]

@wangweij Since your change was applied there have been 7 commits pushed to the master branch:

• 1f556d2: 8258380: [JVMCI] don't clear InstalledCode reference when unloading JVMCI nmethods
• e7aa5fe: 8258427: Problem List some tests related to FileDialog for MacOS
• e911351: 8258140: Update @jls tags in java.base for renamed/renumbered sections
• ce36aea: 8257822: C2 crashes with SIGFPE due to a division that floats above its zero check
• fa1cbb4: 8258404: Restore stacktrace reuse after 8258094
• 7ff9c85: 8258242: Type profile pollution occurs when memory segments of different kinds are used
• 09e8675: 8255381: com/sun/jdi/EATests.java should not suspend graal threads

Your commit was automatically rebased without conflicts.

Pushed as commit b97fe6c.

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