JDK-8248379 : Handshake closures for JVMTI monitor functions lack of some validations
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 15,16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-06-26
  • Updated: 2020-07-02
  • Resolved: 2020-06-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 16
16 b04Fixed
Related Reports
Relates :  
JDK-8242425 - JVMTI monitor operations should use Thread-Local Handshakes
Description
JDK-8242425 introduces to migrate to thread local handshake from VM operation for GetOwnedMonitorInfo, GetOwnedMonitorStackDepthInfo, and GetCurrentContendedMonitor JVMTI functions. However it lacks of validations for thread state and thread oop of the target.

They were validated when it was performed in VM operations. It should be validated even if they are performed in handshakes.
Comments
Changeset: 5ad963cf Author: Yasumasa Suenaga <ysuenaga@openjdk.org> Date: 2020-06-29 13:35:45 +0000 URL: https://git.openjdk.java.net/mobile/commit/5ad963cf
02-07-2020
URL: https://hg.openjdk.java.net/jdk/jdk/rev/2163ccf44b2a User: ysuenaga Date: 2020-06-29 04:36:28 +0000
29-06-2020