8190753: (zipfs): Accessing a large entry (> 2^31 bytes) leads to a negative initial size for ByteArrayOutputStream

[apavlyutkin]

I'd like to backport JDK-8190753 to jdk13u for parity with jdk15u.

The original patch applied with minor changes:

• eliminated using of unsupported instanceof pattern matching feature

Functionality was tested with accompanying

• ./test/jdk/jdk/nio/zipfs/LargeCompressedEntrySizeTest.java
• ./test/jdk/jdk/nio/zipfs/ZipFSOutputStreamTest.java

Regression: jdk_tier2

---

Progress

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

Issue

• JDK-8190753: (zipfs): Accessing a large entry (> 2^31 bytes) leads to a negative initial size for ByteArrayOutputStream

Reviewers

• Yuri Nesterenko (@yan-too - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 275

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

Using diff file

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

[apavlyutkin]

/covered

[bridgekeeper]

Hi @apavlyutkin, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user apavlyutkin" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

[bridgekeeper]

Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (13cd2bb6)

[openjdk]

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

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

8190753: (zipfs): Accessing a large entry (> 2^31 bytes) leads to a negative initial size for ByteArrayOutputStream

Reviewed-by: yan

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

• fc47013: 8274407: (tz) Update Timezone Data to 2021c
• 9aa1e47: 8223173: Implement fast class initialization checks on AARCH64
• f400e59: 8230307: ZGC: Make zGlobals and zArguments OS agnostic
• b94739b: 8269850: Most JDK releases report macOS version 12 as 10.16 instead of 12.0
• f31939c: 8253702: BigSur version number reported as 10.16, should be 11.nn
• f049318: 8225083: Remove Google certificate that is expiring in December 2021
• 9e21dc3: 8225082: Remove IdenTrust certificate that is expiring in September 2021
• 479e5e0: 8274840: Update OS detection code to recognize Windows 11
• 95b11ec: Merge
• 9aa3ee2: 8267729: Improve TLS client handshaking
• ... and 23 more: https://git.openjdk.java.net/jdk13u-dev/compare/e7184740b4c0bc54c6a59ea8950b43740cc01417...master

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 (@yan-too) but any other Committer may sponsor as well.

➡️ 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).

[apavlyutkin]

/integrate

[openjdk]

@apavlyutkin
Your change (at version 13cd2bb) is now ready to be sponsored by a Committer.

[yan-too]

/sponsor

[openjdk]

Going to push as commit 9cd4e47.
Since your change was applied there have been 33 commits pushed to the master branch:

• fc47013: 8274407: (tz) Update Timezone Data to 2021c
• 9aa1e47: 8223173: Implement fast class initialization checks on AARCH64
• f400e59: 8230307: ZGC: Make zGlobals and zArguments OS agnostic
• b94739b: 8269850: Most JDK releases report macOS version 12 as 10.16 instead of 12.0
• f31939c: 8253702: BigSur version number reported as 10.16, should be 11.nn
• f049318: 8225083: Remove Google certificate that is expiring in December 2021
• 9e21dc3: 8225082: Remove IdenTrust certificate that is expiring in September 2021
• 479e5e0: 8274840: Update OS detection code to recognize Windows 11
• 95b11ec: Merge
• 9aa3ee2: 8267729: Improve TLS client handshaking
• ... and 23 more: https://git.openjdk.java.net/jdk13u-dev/compare/e7184740b4c0bc54c6a59ea8950b43740cc01417...master

Your commit was automatically rebased without conflicts.

[openjdk]

@yan-too @apavlyutkin Pushed as commit 9cd4e47.

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