-
Notifications
You must be signed in to change notification settings - Fork 106
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
8321509: False positive in get_trampoline fast path causes crash #864
8321509: False positive in get_trampoline fast path causes crash #864
Conversation
👋 Welcome back dlutker! A progress list of the required criteria for merging this PR into |
@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:
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 31 new commits pushed to the
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. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
|
/approval request backporting to fix an issue 1 of our customers has seen. There is some risk as there is no regression tests specifically for this bug and the customer repro is infrequent enough it is hard to test outside of production. Ran tier1-4 as well as jcstress -m quick on aarch64. |
@lutkerd usage: |
/approval request backporting to fix an issue 1 of our customers has seen. There is some risk as there is no regression tests specifically for this bug and the customer repro is infrequent enough it is hard to test outside of production. Ran tier1-4 as well as jcstress -m quick on aarch64. |
@lutkerd Can you please backport this to jdk23u first? Thanks! |
/integrate |
/sponsor |
Going to push as commit 4989165.
Your commit was automatically rebased without conflicts. |
@benty-amzn @lutkerd Pushed as commit 4989165. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
We have a customer experiencing this crash in 21.0.3 with the same stack as the duplicate issue (JDK-8334136).
Ran tier1-4 on Linux aarch64 as well as a
jcstress -m quick
.Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/864/head:pull/864
$ git checkout pull/864
Update a local copy of the PR:
$ git checkout pull/864
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/864/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 864
View PR using the GUI difftool:
$ git pr show -t 864
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/864.diff
Webrev
Link to Webrev Comment