7036144: GZIPInputStream readTrailer uses faulty available() test for end-of-stream

[toddjonker]

This is a clean backport of d3f3011, originally authored by @archiecobbs and reviewed by @jaikiran

I believe this should be covered by CSR https://bugs.openjdk.org/browse/JDK-8340729 though (as noted there) the description and issue metadata differ regarding JDK21.

Testing:

• New regression test fails without the fix, passes with it
• linux-x86_64-server-release: headless tiers 1-3

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change requires CSR request JDK-8340729 to be approved
• JDK-7036144 needs maintainer approval

Issues

• JDK-7036144: GZIPInputStream readTrailer uses faulty available() test for end-of-stream (Bug - P4 - Approved)
• JDK-8340729: GZIPInputStream readTrailer uses faulty available() test for end-of-stream (CSR)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1897/head:pull/1897
$ git checkout pull/1897

Update a local copy of the PR:
$ git checkout pull/1897
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1897/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1897

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1897.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

7036144: GZIPInputStream readTrailer uses faulty available() test for end-of-stream

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

• 26e4e14: 8249825: Tests sun/security/ssl/SSLSocketImpl/SetClientMode.java and NonAutoClose.java marked with @ignore
• f1a2b4a: 8340185: Use make -k on GHA to catch more build errors
• 70e4cb7: Merge
• ... and 32 more: https://git.openjdk.org/jdk21u-dev/compare/3711d2b8cf114667293f1c8443ffbdc55068f5cc...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.

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

[openjdk]

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

[openjdk]

At least one of the issues associated with this backport has a resolved CSR for a different version. As this means that this backport may also need a CSR, the csr label is being added to this pull request to signal this potential requirement. The command /csr unneeded can be used to remove the label in case a CSR is not needed.

[openjdk]

⚠️ @toddjonker This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (4bf6edab)