RFR: 8373025: Test: test/hotspot/jtreg/gc/cslocker/TestCSLocker.java may deadlock [v2]

[Axel Boldt-Christmas]

> The main threads call to `csLocker.unlock();` may cause an allocation which may trigger a GC. This can lead to a deadlock because we have a native thread which is waiting on a signal from the main thread (which is sent in `csLocker.unlock()`) to `ReleasePrimitiveArrayCritical`. Without the call to ReleasePrimitiveArrayCritical the some GCs may be blocked.
> 
> I suggest we remove the dependency on a java thread for the `GetPrimitiveArrayCritical` / `ReleasePrimitiveArrayCritical` pair. And simply do the lock and the sleep inside native.
> 
> * Testing
>   * Stress testing test/hotspot/jtreg/gc/cslocker/TestCSLocker.java with both SerialGC and ZGC and small heap sizes
>   * GHA

Axel Boldt-Christmas has updated the pull request incrementally with one additional commit since the last revision:

  Remove unused variable

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/28638/files
  - new: https://git.openjdk.org/jdk/pull/28638/files/f4707170..62d34e96

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=28638&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28638&range=00-01

  Stats: 1 line in 1 file changed: 0 ins; 1 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/28638.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/28638/head:pull/28638

PR: https://git.openjdk.org/jdk/pull/28638