-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8349374: [JVMCI] concurrent use of HotSpotSpeculationLog can crash #23444
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
Conversation
|
👋 Welcome back never! A progress list of the required criteria for merging this PR into |
|
@tkrodriguez 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 17 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. ➡️ To integrate this PR with the above commit message to the |
|
@tkrodriguez The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
| return; | ||
| } | ||
|
|
||
| if (UnsafeAccess.UNSAFE.getLong(getFailedSpeculationsAddress()) != 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still possible for getFailedSpeculationsAddress() to return 0 (i.e. when managesFailedSpeculations is false). So I think this should be:
diff --git a/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotSpeculationLog.java b/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotSpeculationLog.java
index fd46e281c3b..a861c00d77d 100644
--- a/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotSpeculationLog.java
+++ b/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotSpeculationLog.java
@@ -171,8 +171,9 @@ public String toString() {
@Override
public void collectFailedSpeculations() {
- if (failedSpeculationsAddress != 0 && UnsafeAccess.UNSAFE.getLong(failedSpeculationsAddress) != 0) {
- failedSpeculations = compilerToVM().getFailedSpeculations(failedSpeculationsAddress, failedSpeculations);
+ long address = getFailedSpeculationsAddress();
+ if (address != 0 && UnsafeAccess.UNSAFE.getLong(address) != 0) {
+ failedSpeculations = compilerToVM().getFailedSpeculations(address, failedSpeculations);
assert failedSpeculations.getClass() == byte[][].class;
}
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm filtering out 0 above this line and getFailedSpeculationsAddress() can't return 0 if failedSpeculationsAddress is already non-zero.
failedSpeculationsAddress also can't be 0 if managesFailedSpeculations is false since we throw IllegalArgumentException in that case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
failedSpeculationsAddressalso can't be 0 ifmanagesFailedSpeculationsis false since we throwIllegalArgumentExceptionin that case.
Ok, I'd forgotten about that invariant. Might be worth reminding the reader of it with a comment in collectFailedSpeculations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the javadoc for getFailedSpeculationsAddress to specify that it always returns non-zero. I also expanded the comments in collectFailedSpeculations and call getFailedSpeculationsAddress() to get the value. I think it's clearer what's going on now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine.
|
Thanks! /integrate |
|
Going to push as commit 7f6c687.
Your commit was automatically rebased without conflicts. |
|
@tkrodriguez Pushed as commit 7f6c687. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This ensures that collectFailedSpeculations sees the initialization of the recently allocated failedSpeculationsAddress memory.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23444/head:pull/23444$ git checkout pull/23444Update a local copy of the PR:
$ git checkout pull/23444$ git pull https://git.openjdk.org/jdk.git pull/23444/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23444View PR using the GUI difftool:
$ git pr show -t 23444Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23444.diff
Using Webrev
Link to Webrev Comment