Skip to content

8325372: Shenandoah: SIGSEGV crash in unnecessary_acquire due to LoadStore split through phi #306

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

Closed

Conversation

lutkerd
Copy link

@lutkerd lutkerd commented Feb 29, 2024

Backporting to 21 which also has the same issue.

Ran tier1, 2, 3, 4 on linux aarch64 with -XX:+UseShenandoahGC as well as jcstress quick.


Progress

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

Issue

  • JDK-8325372: Shenandoah: SIGSEGV crash in unnecessary_acquire due to LoadStore split through phi (Bug - P4 - Approved)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 306

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 29, 2024

👋 Welcome back dlutker! 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 openjdk bot changed the title Backport 5d414da50459b7a1e6f0f537ff3b318854b2c427 8325372: Shenandoah: SIGSEGV crash in unnecessary_acquire due to LoadStore split through phi Feb 29, 2024
@openjdk
Copy link

openjdk bot commented Feb 29, 2024

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

@lutkerd lutkerd marked this pull request as ready for review March 4, 2024 22:55
@openjdk
Copy link

openjdk bot commented Mar 4, 2024

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

@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 4, 2024
@mlbridge
Copy link

mlbridge bot commented Mar 4, 2024

Webrevs

@lutkerd
Copy link
Author

lutkerd commented Mar 5, 2024

/approval request Backport to resolve a handful of customer reports. Ran Tier 1,2,3 and 4 as well as jcstress -m quick with -XX:+UseShenandoahGC and did not hit any issues.

@openjdk
Copy link

openjdk bot commented Mar 5, 2024

@lutkerd
8325372: The approval request has been created successfully.

@openjdk openjdk bot added approval and removed approval labels Mar 5, 2024
@lutkerd lutkerd closed this Mar 12, 2024
@lutkerd lutkerd force-pushed the backport-lutkerd-5d414da5 branch from b4c0643 to d4e336d Compare March 12, 2024 21:58
@lutkerd lutkerd reopened this Mar 12, 2024
@openjdk
Copy link

openjdk bot commented Mar 12, 2024

@lutkerd 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.

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.

While the patch is still relatively new in mainline, I think this one is good to have earlier in 21u-dev. This is going to be additionally tested by our 21u pipelines, in addition to mainline testing.

There is a GHA failure in x86_32 StringRepeat test, but it does not look relevant.

@lutkerd
Copy link
Author

lutkerd commented Mar 13, 2024

/approval request Backport to resolve a handful of customer reports. Ran Tier 1,2,3 and 4 as well as jcstress -m quick with -XX:+UseShenandoahGC and did not hit any issues. GHA failures is not related to this change and didn't fail on initial run, rerunning to be safe.

@openjdk
Copy link

openjdk bot commented Mar 13, 2024

@lutkerd
8325372: The approval request has been updated successfully.

@openjdk openjdk bot added the approval label Mar 13, 2024
@openjdk
Copy link

openjdk bot commented Mar 13, 2024

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

8325372: Shenandoah: SIGSEGV crash in unnecessary_acquire due to LoadStore split through phi

Reviewed-by: shade

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

  • e3b6098: 8322503: Shenandoah: Clarify gc state usage
  • 93fd1a1: 8324238: [macOS] java/awt/Frame/ShapeNotSetSometimes/ShapeNotSetSometimes.java fails with the shape has not been applied msg
  • ad5a087: 8321815: Shenandoah: gc state should be synchronized to java threads only once per safepoint
  • 608c98d: 8326496: [test] checkHsErrFileContent support printing hserr in error case
  • d42da09: 8325743: test/jdk/java/nio/channels/unixdomain/SocketOptions.java enhance user name output in error case
  • 2a6688f: 8320129: "top" command during jtreg failure handler does not display CPU usage on OSX
  • da02da7: 8325432: enhance assert message "relocation addr must be in this section"

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 (@shipilev) 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 added ready Pull request is ready to be integrated and removed approval labels Mar 14, 2024
@lutkerd
Copy link
Author

lutkerd commented Mar 14, 2024

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Mar 14, 2024
@openjdk
Copy link

openjdk bot commented Mar 14, 2024

@lutkerd
Your change (at version 80c0966) is now ready to be sponsored by a Committer.

@phohensee
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Mar 14, 2024

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Mar 14, 2024
@openjdk openjdk bot closed this Mar 14, 2024
@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 Mar 14, 2024
@openjdk
Copy link

openjdk bot commented Mar 14, 2024

@phohensee @lutkerd Pushed as commit cc65d0d.

💡 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 clean integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants