Skip to content

8347911: Limit the length of inflated text chunks#687

Closed
TimPushkin wants to merge 1 commit intoopenjdk:masterfrom
TimPushkin:8347911-jdk8
Closed

8347911: Limit the length of inflated text chunks#687
TimPushkin wants to merge 1 commit intoopenjdk:masterfrom
TimPushkin:8347911-jdk8

Conversation

@TimPushkin
Copy link
Copy Markdown
Contributor

@TimPushkin TimPushkin commented Sep 1, 2025

Backport of JDK-8347911 for parity with Oracle's JDK 8u461.

Conflicts:

  • Copyright years
  • Missing JDK-8139206: use IOUtils.readNBytes(...) instead of the missing InputStream.readNBytes(...)

Testing: GitHub CI, jdk_imageio test group locally (headless linux/arm64)


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8347911 needs maintainer approval

Issue

  • JDK-8347911: Limit the length of inflated text chunks (Bug - P3 - Approved)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 687

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Sep 1, 2025

👋 Welcome back tpushkin! A progress list of the required criteria for merging this PR into pr/686 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Sep 1, 2025

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

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

8347911: Limit the length of inflated text chunks

Reviewed-by: sgehwolf

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 1 new commit pushed to the master branch:

  • b647fb8: 8375063: Update Libpng to 1.6.54

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.

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 (@jerboaa) 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).

@openjdk openjdk Bot changed the title Backport 398a580518b4e7961bdddf733e0a89ff25bc437a 8347911: Limit the length of inflated text chunks Sep 1, 2025
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Sep 1, 2025

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

@openjdk openjdk Bot added backport Port of a pull request already in a different code base rfr Pull request is ready for review labels Sep 1, 2025
@mlbridge
Copy link
Copy Markdown

mlbridge Bot commented Sep 1, 2025

Webrevs

@TimPushkin
Copy link
Copy Markdown
Contributor Author

I believe the test failures are not related

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Sep 30, 2025

@TimPushkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/touch

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Sep 30, 2025

@TimPushkin The pull request is being re-evaluated and the inactivity timeout has been reset.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Oct 28, 2025

@TimPushkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/touch

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Oct 28, 2025

@TimPushkin The pull request is being re-evaluated and the inactivity timeout has been reset.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Nov 26, 2025

@TimPushkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/touch

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Nov 26, 2025

@TimPushkin The pull request is being re-evaluated and the inactivity timeout has been reset.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Dec 24, 2025

@TimPushkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/touch

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Dec 24, 2025

@TimPushkin The pull request is being re-evaluated and the inactivity timeout has been reset.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Dec 26, 2025

@TimPushkin this pull request can not be integrated into pr/686 due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout 8347911-jdk8
git fetch https://git.openjdk.org/jdk8u-dev.git pr/686
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge pr/686"
git push

@openjdk openjdk Bot added the merge-conflict Pull request has merge conflict with target branch label Dec 26, 2025
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Dec 26, 2025

@TimPushkin Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@openjdk openjdk Bot removed the merge-conflict Pull request has merge conflict with target branch label Dec 26, 2025
@TimPushkin
Copy link
Copy Markdown
Contributor Author

Rebased on top of the current master.

The CI failure is a single unrelated GC test, already reported as JDK-8303159.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Jan 23, 2026

@TimPushkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/keepalive

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Jan 26, 2026

@TimPushkin The pull request is being re-evaluated and the inactivity timeout has been reset.

@gnu-andrew
Copy link
Copy Markdown
Member

I'll review this one once #686 is in.

@gnu-andrew
Copy link
Copy Markdown
Member

I agree the test failure seems unrelated to this change.

@openjdk-notifier openjdk-notifier Bot changed the base branch from pr/686 to master February 18, 2026 01:41
@openjdk-notifier
Copy link
Copy Markdown

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout 8347911-jdk8
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

@openjdk openjdk Bot added the merge-conflict Pull request has merge conflict with target branch label Feb 18, 2026
Backport-of: 398a580518b4e7961bdddf733e0a89ff25bc437a
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

@TimPushkin Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@openjdk openjdk Bot removed the merge-conflict Pull request has merge conflict with target branch label Feb 18, 2026
@TimPushkin
Copy link
Copy Markdown
Contributor Author

Rebased without changes to the commit being backported

Copy link
Copy Markdown
Contributor

@jerboaa jerboaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

⚠️ @TimPushkin 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.

@TimPushkin
Copy link
Copy Markdown
Contributor Author

/approval request Backporting for parity with Oracle.
Low risk: the change is limited to image IO, conflicts are minor.
Testing: GitHub CI, jdk_imageio test group locally (headless linux/arm64)

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

@TimPushkin
8347911: The approval request has been created successfully.

@openjdk openjdk Bot added the approval Requires approval; will be removed when approval is received label Feb 18, 2026
@jerboaa
Copy link
Copy Markdown
Contributor

jerboaa commented Feb 18, 2026

/approve yes

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

@jerboaa
8347911: The approval request has been approved.

@openjdk openjdk Bot added ready Pull request is ready to be integrated and removed approval Requires approval; will be removed when approval is received labels Feb 18, 2026
@TimPushkin
Copy link
Copy Markdown
Contributor Author

/integrate

@openjdk openjdk Bot added the sponsor Pull request is ready to be sponsored label Feb 18, 2026
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

@TimPushkin
Your change (at version 5d487ee) is now ready to be sponsored by a Committer.

@jerboaa
Copy link
Copy Markdown
Contributor

jerboaa commented Feb 18, 2026

/sponsor

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

Going to push as commit 829387f.
Since your change was applied there has been 1 commit pushed to the master branch:

  • b647fb8: 8375063: Update Libpng to 1.6.54

Your commit was automatically rebased without conflicts.

@openjdk openjdk Bot added the integrated Pull request has been integrated label Feb 18, 2026
@openjdk openjdk Bot closed this Feb 18, 2026
@openjdk openjdk Bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Feb 18, 2026
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 18, 2026

@jerboaa @TimPushkin Pushed as commit 829387f.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Port of a pull request already in a different code base integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

4 participants