8270317: Large Allocation in CipherSuite

[cliveverghese]

Hi all,

this pull request contains a backport of commit e627caec from the openjdk/jdk repository.

The commit being backported was authored by Clive Verghese on 24 Jul 2021 and was reviewed by Xue-Lei Andrew Fan and Volker Simonis.

We have tested this change in production regions internally for 3 months.

Thanks!

---

Progress

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

Issue

• JDK-8270317: Large Allocation in CipherSuite

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk15u-dev pull/95/head:pull/95
$ git checkout pull/95

Update a local copy of the PR:
$ git checkout pull/95
$ git pull https://git.openjdk.java.net/jdk15u-dev pull/95/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 95

View PR using the GUI difftool:
$ git pr show -t 95

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk15u-dev/pull/95.diff

[bridgekeeper]

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

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@cliveverghese This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8270317: Large Allocation in CipherSuite

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (ee529b65)

[yan-too]

@cliveverghese (skip if you know it:-) as of now, the process does require some modifications in JDK-827017: put there so called Fix request for every update release train and (usually after testing with that release finished,) jdkNN-fix-request label. A maintainer would answer by jdkNN-fix-yes, and a committer would push.

[cliveverghese]

/integrate

[openjdk]

@cliveverghese
Your change (at version ee529b6) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

[openjdk]

Going to push as commit 5c9dc7b.

[openjdk]

@phohensee @cliveverghese Pushed as commit 5c9dc7b.

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