-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8285794: AsyncGetCallTrace might acquire a lock via JavaThread::thread_from_jni_environment #8446
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
Calling JavaThread::thread_from_jni_environment for a terminated thread might cause the aquisition of a lock. Calling JavaThread::current does not have this problem and AsyncGetCallTrace can only be called on the current thread anyway.
👋 Welcome back parttimenerd! A progress list of the required criteria for merging this PR into |
@parttimenerd 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
|
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.
Looks good.
Thanks.
@parttimenerd 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 128 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 (@dholmes-ora, @TheRealMDoerr, @jbachorik) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@parttimenerd |
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.
LGTM.
/integrate |
@parttimenerd |
/sponsor |
Going to push as commit d4474b5.
Your commit was automatically rebased without conflicts. |
@TheRealMDoerr @parttimenerd Pushed as commit d4474b5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Calling JavaThread::thread_from_jni_environment for a terminated thread in AsyncGetCallTrace might cause the acquisition of a lock, making AsyncGetCallTrace non-signal-safe.
AsyncGetCallTrace can only be called for the current threads (there are asserts for that), therefore using JavaThread::current directly and checking the termination status is semantically equivalent.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8446/head:pull/8446
$ git checkout pull/8446
Update a local copy of the PR:
$ git checkout pull/8446
$ git pull https://git.openjdk.java.net/jdk pull/8446/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8446
View PR using the GUI difftool:
$ git pr show -t 8446
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8446.diff