-
Notifications
You must be signed in to change notification settings - Fork 148
8331735: UpcallLinker::on_exit races with GC when copying frame anchor #1424
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 andrew! A progress list of the required criteria for merging this PR into |
|
@gnu-andrew 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 14 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 |
|
This backport pull request has now been updated with issues from the original commit. |
|
|
|
/approval request Clean backport of a fix for a race condition in the FFM API. Can lead to crashes when the FFM code manipulates a frame anchor in native mode, which the GC does not expect to happen. Fix is to move the frame anchor copying to Java mode, where the GC will wait for the thread to get to a safepoint. Risk to other code is low as the UpcallLinker is only used by FFM. |
|
@gnu-andrew |
|
@gnu-andrew, you might want to push this, today 18:00 CET the last automatic merge from jdk21u-dev to jdk21u will happen. |
Ah, sorry, I got my dates mixed up and thought that was next week. I've been away the first half of this week, so only been able to get back to this today. |
|
/integrate |
|
Going to push as commit 91457e6.
Your commit was automatically rebased without conflicts. |
|
@gnu-andrew Pushed as commit 91457e6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Clean backport of a fix for a race condition in code adapted from
JavaCallWrapperfor the FFM API. This is more visible in 22 and later, where FFM is fully supported and the OpenType implementation using HarfBuzz has been ported to use it. However, the copy in the native state seems to have been introduced as far back as JDK-8269240 in 17 when theJavaCallWrappercode was ported to what was thenuniversalUpcallHandler.cpp.Progress
Issues
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1424/head:pull/1424$ git checkout pull/1424Update a local copy of the PR:
$ git checkout pull/1424$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1424/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1424View PR using the GUI difftool:
$ git pr show -t 1424Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1424.diff
Using Webrev
Link to Webrev Comment