8373627: assert(!is_vthread_transition_disabler()) failed: no suspend allowed for vthread transition disablers

[sspitsyn]

This is a 1-liner fix of a regression.
The issue was discovered after merge with main line of this PR: #28407 .

It will need to be back ported to 26 as well.

Testing:

• TBD: This was already tested in another PR repo but will submit mach5 tiers 1-3 to be completely safe.

---

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

Issue

• JDK-8373627: assert(!is_vthread_transition_disabler()) failed: no suspend allowed for vthread transition disablers (Bug - P4)

Reviewers

• Patricio Chilano Mateo (@pchilano - Reviewer)
• David Holmes (@dholmes-ora - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28805/head:pull/28805
$ git checkout pull/28805

Update a local copy of the PR:
$ git checkout pull/28805
$ git pull https://git.openjdk.org/jdk.git pull/28805/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28805

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28805.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8373627: assert(!is_vthread_transition_disabler()) failed: no suspend allowed for vthread transition disablers

Reviewed-by: pchilanomate, dholmes

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

• 3f33eaa: 8373649: Convert simple AtomicAccess usage in ConcurrentHashTable to use Atomic
• 1748737: 8372988: Test runtime/Nestmates/membership/TestNestHostErrorWithMultiThread.java failed: Unexpected interrupt
• 317788f: 8360160: ubuntu-22-04 machine is failing client tests
• ... and 118 more: https://git.openjdk.org/jdk/compare/15f25389435288881644f7aeab48fd2eae410999...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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@sspitsyn The following label will be automatically applied to this pull request:

• hotspot-runtime

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (3f610aa3)

[pchilano]

Thanks for finding and fixing this Serguei!

[dholmes-ora]

LGTM

Thanks

[sspitsyn]

Thank you for reviews, David and Patricio!

[sspitsyn]

/integrate

[openjdk]

Going to push as commit 53ebcdb.
Since your change was applied there have been 126 commits pushed to the master branch:

• 41d28c1: 8373561: Replace usages of -verify java launcher option with -Xverify:all JVM option
• 43d4456: 8373570: Javac stack overflow on method-local class with nested record referring to enclosing type
• 8402891: 8373355: C2: CompileCommand PrintIdealPhase should also print nodes that are not "reachable from below"
• ... and 123 more: https://git.openjdk.org/jdk/compare/15f25389435288881644f7aeab48fd2eae410999...master

Your commit was automatically rebased without conflicts.

[openjdk]

@sspitsyn Pushed as commit 53ebcdb.

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

[sspitsyn]

/backport :jdk26

[openjdk]

@sspitsyn the backport was successfully created on the branch backport-sspitsyn-53ebcdbd-jdk26 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk26, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 53ebcdbd from the openjdk/jdk repository.

The commit being backported was authored by Serguei Spitsyn on 16 Dec 2025 and was reviewed by Patricio Chilano Mateo and David Holmes.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-sspitsyn-53ebcdbd-jdk26:backport-sspitsyn-53ebcdbd-jdk26
$ git checkout backport-sspitsyn-53ebcdbd-jdk26
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-sspitsyn-53ebcdbd-jdk26

⚠️ @sspitsyn You are not yet a collaborator in my fork openjdk-bots/jdk. An invite will be sent out and you need to accept it before you can proceed.