JDK-8264800 : cleanup Threads_lock comments in JVM/TI function headers
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2021-04-06
  • Updated: 2021-06-07
  • Resolved: 2021-06-01
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 17
17 b25Fixed
Related Reports
Relates :  
JDK-8167108 - inconsistent handling of SR_lock can lead to crashes
Description
JVM/TI files like  src/hotspot/share/prims/jvmtiEnv.cpp have
comments like these:

// Threads_lock NOT held, java_thread not protected by lock

These should have been taken care of by a follow up bug after
the Thread-SMR project, but it looks like I forgot to file the bug.
Comments
Changeset: 40e4171f Author: Daniel D. Daugherty <dcubed@openjdk.org> Date: 2021-06-01 18:51:40 +0000 URL: https://git.openjdk.java.net/jdk/commit/40e4171f562da2f6a507efc7ad359e298199ed71
01-06-2021