8268361: Fix the infinite loop in next_line

[akashche]

Clean backport of a minor fix. Testing: ran jtreg:jdk_management on Linux.

---

Progress

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

Issue

• JDK-8268361: Fix the infinite loop in next_line

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u pull/130/head:pull/130
$ git checkout pull/130

Update a local copy of the PR:
$ git checkout pull/130
$ git pull https://git.openjdk.java.net/jdk17u pull/130/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 130

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u/pull/130.diff

[bridgekeeper]

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

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

8268361: Fix the infinite loop in next_line

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 (836bf788)

[bridgekeeper]

@akashche 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 add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[akashche]

Gentle reminder, it would be great if someone can review this backport.

[phohensee]

Clean backports don't need review. Just tag the JBS issue.

[akashche]

Marked the bug for approval.

[akashche]

/integrate

[openjdk]

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

• 4003db8: 8268464: Remove dependancy of TestHttpsServer, HttpTransaction, HttpCallback from open/test/jdk/sun/net/www/protocol/https/ tests
• 229cb35: 8269216: Useless initialization in com/sun/crypto/provider/PBES2Parameters.java
• de47488: 8270290: NTLM authentication fails if HEAD request is used
• 802844a: 8276066: Reset LoopPercentProfileLimit for x86 due to suboptimal performance
• a0899bf: 8274848: LambdaMetaFactory::metafactory on REF_invokeSpecial impl method has incorrect behavior
• 583844a: 8275302: unexpected compiler error: cast, intersection types and sealed
• 0364737: 8276122: Change openjdk project in jcheck to jdk-updates
• 25bfea6: 8276130: Fix Github Actions of JDK17u to account for update version scheme
• 22f1513: 8273575: memory leak in appendBootClassPath(), paths must be deallocated
• 38bfd62: 8273965: some testlibrary_tests/ir_framework tests fail when c1 disabled
• ... and 118 more: https://git.openjdk.java.net/jdk17u/compare/c136c188b519aa315985c9dd0bbe9fedbf182175...master

Your commit was automatically rebased without conflicts.

[openjdk]

@akashche Pushed as commit 9f3c840.

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