> This is a fix of one more deadlock issue related to `interruptLock` critical > sections. When the `interruptLock` is hold by the target virtual thread it is > unsafe to suspend or post JVMTI events. This update is to ignore the JVMTI > events when the `interruptLock` is hold. It is additionally to the cases when > the target JavaThread is in a `VTMS` transition. It is based on the existing > mechanism disallowing JVMTI suspends while the `interruptLock` is hold. In > order to support this the target JavaThread has the `_is_disable_suspend` bit. > > Testing: > - Ran mach5 tiers 1-6 > - There is no regression test for this issue as it is not hard to construct > one. Originally, the issue was reported by JGroups which is using the `Async` > profiler.
Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision: review: fixed a typo in new comment ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22997/files - new: https://git.openjdk.org/jdk/pull/22997/files/46527318..a85b5985 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22997&range=03 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22997&range=02-03 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22997.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22997/head:pull/22997 PR: https://git.openjdk.org/jdk/pull/22997
