Skip to content

8343607: C2: Shenandoah crashes during barrier expansion in Continuation::enter #2029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

JohnTortugo
Copy link
Contributor

@JohnTortugo JohnTortugo commented Aug 1, 2025

Clean backport of this shenandoah c2 fix. We hit this bug in our (Amazon) internal CI system and also was reported by RedHat to happen on their CI as well.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8343607 needs maintainer approval

Issue

  • JDK-8343607: C2: Shenandoah crashes during barrier expansion in Continuation::enter (Bug - P4 - Requested)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2029

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 1, 2025

👋 Welcome back cslucas! 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
Copy link

openjdk bot commented Aug 1, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk bot added the rfr Pull request is ready for review label Aug 1, 2025
@mlbridge
Copy link

mlbridge bot commented Aug 1, 2025

Webrevs

@shipilev
Copy link
Member

shipilev commented Aug 4, 2025

Two things:

  1. Merge from current jdk21u-dev master to the GHA cross-compilation jobs fixed.
  2. The PR itself should be named Backport 45c914c3ad8fbc406af9ba9dec97f11c28c91299, not the commit only. This would get it properly recognized as backport.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

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

The backport itself looks fine. I suspect bots would mark it as clean once they recognize it as backport.

@openjdk
Copy link

openjdk bot commented Aug 4, 2025

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

@JohnTortugo JohnTortugo changed the title 8343607: C2: Shenandoah crashes during barrier expansion in Continuation::enter Backport 45c914c3ad8fbc406af9ba9dec97f11c28c91299 Aug 6, 2025
@openjdk openjdk bot changed the title Backport 45c914c3ad8fbc406af9ba9dec97f11c28c91299 8343607: C2: Shenandoah crashes during barrier expansion in Continuation::enter Aug 6, 2025
@openjdk
Copy link

openjdk bot commented Aug 6, 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 clean Identical backport; no merge resolution required labels Aug 6, 2025
@shipilev
Copy link
Member

shipilev commented Aug 7, 2025

Also, if you merge with upstream master, the GHA jobs would be fixed.

@openjdk openjdk bot added the approval Requires approval; will be removed when approval is received label Aug 12, 2025
@GoeLin
Copy link
Member

GoeLin commented Aug 12, 2025

Hi @JohnTortugo
you don't need to open a backport JBS issue. It does no harm if you do that, but except for rare cases (if you need a CSR) it's done automatically by Skara. But if you opened one Skara will pick it up automaticaly.
But please don't add a fix version, that is set automatically. Currently, we are developing for 21.0.9. If you want to get your change to 21.0.10, you can withdraw and request approval again in two weeks.

@shipilev
Copy link
Member

@GoeLin -- from the internal discussion, I believe Cesar (who is currently outside business hours) intended to backport it for 21.0.9; it is just a process hiccup. So I just marked the approval request to get it on maintainers radar. Thanks!

@JohnTortugo
Copy link
Contributor Author

Thank you for the advice @GoeLin ; thank you Aleksey for clarifying the intent here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approval Requires approval; will be removed when approval is received backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

3 participants