JDK-8272447 : Remove 'native' ranked Mutex
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-08-13
  • Updated: 2021-08-31
  • Resolved: 2021-08-25
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 18
18 b12Fixed
Related Reports
Blocks :  
JDK-8272480 - Remove Mutex::access rank
Description
There are two Mutexes now that are 'native' rank in the JVM source code, and a few in the gtests. They should have a real rank and participate in deadlock detection.

If we want to have a 'native' rank for locks to not participate in resource cycle deadlock detection, that rank should be at the lower end of the hierarchy, where 'access' rank is.  Having 'native' be the high end of the hierarchy makes comparison operators awkward.
Comments
Changeset: 2ef68711 Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2021-08-25 13:25:34 +0000 URL: https://git.openjdk.java.net/jdk/commit/2ef6871118109b294e3148c8f15d4335039dd121
25-08-2021