-
Notifications
You must be signed in to change notification settings - Fork 233
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
8276125: RunThese24H.java SIGSEGV in JfrThreadGroup::thread_group_id #2501
Conversation
👋 Welcome back jia-wei-tang! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
89e822d
to
a929af3
Compare
@jia-wei-tang 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. |
/integrate |
@jia-wei-tang This pull request has not yet been marked as ready for integration. |
Is there any reviewer available to help with the review? Thanks a lot! |
Please get a review before labeling fix-request. |
@GoeLin Could you help with this review? In our application, we can stably reproduce this JVM crash. And this PR just backport a null condition check from JDK17. This is really simple and harmless. Thank you very much. |
|
@jia-wei-tang This change now passes all automated pre-integration checks. 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 79 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. Possible candidates are the reviewers of this PR (@mgronlun) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@jia-wei-tang |
/sponsor |
Going to push as commit a4a5c7f.
Your commit was automatically rebased without conflicts. |
@DamonFool @jia-wei-tang Pushed as commit a4a5c7f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
It isn't a clean backport for two reasons.
parent_thread_group_handle != NULL
will cause a compile error without a type cast.This backport prevents a JFR operation from accessing an illegal address which has not be filled before the initialization of a JavaThread, which is created from a JNI interface.
The risk is very low since it only adds a null pointer check. Besides, This backport has be accepted in jdk17-dev.
Additional testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/2501/head:pull/2501
$ git checkout pull/2501
Update a local copy of the PR:
$ git checkout pull/2501
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/2501/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2501
View PR using the GUI difftool:
$ git pr show -t 2501
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/2501.diff
Webrev
Link to Webrev Comment