Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

jia-wei-tang
Copy link
Contributor

@jia-wei-tang jia-wei-tang commented Jan 30, 2024

It isn't a clean backport for two reasons.

  1. jdk11 cannot use nullptr, so it should use NULL instead.
  2. 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:

  • Linux aarch64 server fastdebug, test/jdk/jdk/jfr passed

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8276125 needs maintainer approval

Issue

  • JDK-8276125: RunThese24H.java SIGSEGV in JfrThreadGroup::thread_group_id (Bug - P3 - Approved)

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

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 30, 2024

👋 Welcome back jia-wei-tang! 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 a885aab696777c99c8c4c5d9a46afc5fe0a4fe47 8276125: RunThese24H.java SIGSEGV in JfrThreadGroup::thread_group_id Jan 30, 2024
@openjdk
Copy link

openjdk bot commented Jan 30, 2024

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

@openjdk openjdk bot added backport rfr Pull request is ready for review labels Jan 30, 2024
@mlbridge
Copy link

mlbridge bot commented Jan 30, 2024

Webrevs

@openjdk
Copy link

openjdk bot commented Jan 30, 2024

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

@jia-wei-tang
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Feb 6, 2024

@jia-wei-tang This pull request has not yet been marked as ready for integration.

@jia-wei-tang
Copy link
Contributor Author

Is there any reviewer available to help with the review? Thanks a lot!

@GoeLin
Copy link
Member

GoeLin commented Feb 19, 2024

Please get a review before labeling fix-request.

@openjdk openjdk bot added approval and removed approval labels Feb 19, 2024
@jia-wei-tang
Copy link
Contributor Author

@egahlin @mgronlun Could you help review the backport related to JFR? The reasons for changing the original backport codes and the related Jtreg tests results have been presented before. Thank you very much.

@jia-wei-tang
Copy link
Contributor Author

jia-wei-tang commented Feb 28, 2024

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

@openjdk
Copy link

openjdk bot commented Mar 4, 2024

⚠️ @jia-wei-tang the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout my-backport-branch
$ git commit --author='Preferred Full Name <you@example.com>' --allow-empty -m 'Update full name'
$ git push

@openjdk
Copy link

openjdk bot commented Mar 4, 2024

@jia-wei-tang This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8276125: RunThese24H.java SIGSEGV in JfrThreadGroup::thread_group_id

Reviewed-by: mgronlun

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 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 (@mgronlun) 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 the ready Pull request is ready to be integrated label Mar 4, 2024
@jia-wei-tang
Copy link
Contributor Author

/integrate

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

openjdk bot commented Mar 4, 2024

@jia-wei-tang
Your change (at version e720c8a) is now ready to be sponsored by a Committer.

@DamonFool
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Mar 4, 2024

Going to push as commit a4a5c7f.
Since your change was applied there have been 79 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 4, 2024
@openjdk openjdk bot closed this Mar 4, 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 4, 2024
@openjdk
Copy link

openjdk bot commented Mar 4, 2024

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

@jia-wei-tang jia-wei-tang deleted the my-backport-branch branch March 5, 2024 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants