> Please review this change to fix a problem that can rise if JVM TI suspension > is allowed when a thread is executing in a JNI "critical" region. The gory > details are in the first comment so that the PR emails are shorter > > A new test is introduced to check that we cannot suspend in a critical region > > Other testing: > - Tiers 1-5 on all platforms > > The key insights into this solution are attributed to @pchilano. Everything > simpler I tried was buggy and led me back to Patricio's suggested changes to > the operation filtering. The actual details of this and any remaining bugs in > it are all my own. > > Thanks. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai).
David Holmes has updated the pull request incrementally with one additional commit since the last revision: Use std::atomic for shared variables ------------- Changes: - all: https://git.openjdk.org/jdk/pull/30936/files - new: https://git.openjdk.org/jdk/pull/30936/files/b0f332ab..e5214b8e Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=30936&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30936&range=00-01 Stats: 3 lines in 1 file changed: 1 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/30936.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/30936/head:pull/30936 PR: https://git.openjdk.org/jdk/pull/30936
