RFR: 8354523: runtime/Monitor/SyncOnValueBasedClassTest.java triggers SIGSEGV [v7]

[Boris Ulasevich]

On Mon, 21 Apr 2025 10:44:34 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

>> When DiagnoseSyncOnValueBasedClasses is != 0, then we can take the slow-path without having cleared the monitor cache in the BasicLock. This would later lead to a crash or other unexpected behaviour. This can happen with C1 or the interpreter, C2 has the DiagnoseSyncOnValueBasedClasses-block after clearing the cache, and the native-entry in sharedRuntime_x86_64.cpp does not have a DiagnoseSyncOnValueBasedClasses-block at all.
>> 
>> The proposed fix so far is a bit ugly because it repeats the clearing code in 3 places. The alternative would be to move the DiagnoseSyncOnValueBasedClasses-block into MA::lightweight_lock(), but this would bring DiagnoseSyncOnValueBasedClasses-handling into the native entry in sharedRuntime_x86_64.cpp, which is currently not the case. Also, we don't have enough regs for that, but we can probably use rscratch1 now that 32-bit is gone (as is already done in C1 and interpreter paths anyway).
>> 
>> I'd first settle on the structure, and then implement the same thing for aarch64.
>> ping @xmas92
>
> Roman Kennke has updated the pull request incrementally with one additional commit since the last revision:
> 
>   S390 parts

Hi. Thanks for ping!
I think this change is not appicable to ARM32. JDK-8315884 "New Object to ObjectMonitor mapping" is not supported on arm32, and BasicLock::object_monitor_cache is not used.

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

PR Comment: https://git.openjdk.org/jdk/pull/24660#issuecomment-2819198459