RFR: 8369515: Deadlock between JVMTI and JNI ReleasePrimitiveArrayCritical [v3]

[David Holmes]

> As discussed in JBS the deadlock occurs when the call to `ReleasePrimitiveArrayCritical` performs the transition from native to VM, and in the process checks for special runtime exit conditions - which includes the `obj_deopt_suspend` request. The simple solution is to define a custom JNI ENTRY with custom `ThreadInVMfromNative` that elides the exit check.
> 
> The change is limited to `ReleasePrimitiveArrayCritical` and `ReleaseStringCritical`.
> 
> UPDATE: we are now employing a much simpler solution.
> 
> There is no regression test as this has only been seen in long running stress tests.
> 
> Testing:
>    -tiers 1-6

David Holmes has updated the pull request incrementally with one additional commit since the last revision:

  Exapnd comment

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/28779/files
  - new: https://git.openjdk.org/jdk/pull/28779/files/b96a9bc2..9bc8a3f8

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

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

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