Integrated: 8285794: AsyncGetCallTrace might acquire a lock via JavaThread::thread_from_jni_environment

Mon May 9 08:20:59 UTC 2022

On Thu, 28 Apr 2022 09:38:30 GMT, Johannes Bechberger <duke at openjdk.java.net> wrote:

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

This pull request has now been integrated.

Changeset: d4474b58
Author:    Johannes Bechberger <johannes.bechberger at sap.com>
Committer: Martin Doerr <mdoerr at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/d4474b5816c2ec8daaf1c905b77d8ba4e23c9439
Stats:     7 lines in 1 file changed: 4 ins; 0 del; 3 mod

8285794: AsyncGetCallTrace might acquire a lock via JavaThread::thread_from_jni_environment

Reviewed-by: dholmes, mdoerr, jbachorik

-------------

PR: https://git.openjdk.java.net/jdk/pull/8446