8212155: Race condition when posting dynamic_code_generated event leads to JVM crash

[krk]

Backport of JDK-8212155.

The patch did not apply cleanly due to a merge conflict. The original code JvmtiThreadState::state_for(JavaThread::current()) had already been refactored to JavaThread::current()->jvmti_thread_state() in this branch.

I have also removed the @requires vm.jvmti tag from the test, as it is not supported by the jtreg version in JDK 11.

The DynamicCodeGeneratedTest was confirmed to fail without this patch and passes with it.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8212155 needs maintainer approval

Issue

• JDK-8212155: Race condition when posting dynamic_code_generated event leads to JVM crash (Bug - P3 - Requested)

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/3051/head:pull/3051
$ git checkout pull/3051

Update a local copy of the PR:
$ git checkout pull/3051
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/3051/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3051

View PR using the GUI difftool:
$ git pr show -t 3051

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/3051.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back krk! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (9f252d80)

[krk]

Tagging reviewer of the original commit: @sspitsyn

[shipilev]

Makes sense. Please make sure to run the remaining jvmti tests:

jdk11u-dev/test/hotspot/jtreg/TEST.groups

Lines 462 to 464 in cec1ef0

	# JVMTI tests
	vmTestbase_nsk_jvmti = \
	vmTestbase/nsk/jvmti

jdk11u-dev/test/hotspot/jtreg/TEST.groups

Lines 59 to 60 in cec1ef0

	hotspot_serviceability = \
	serviceability

[openjdk]

⚠️ @krk This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[krk]

==============================
Test summary
==============================
   TEST                                              TOTAL  PASS  FAIL ERROR
   jtreg:test/hotspot/jtreg:vmTestbase_nsk_jvmti       640   640     0     0
   jtreg:test/hotspot/jtreg:hotspot_serviceability     178   178     0     0

[krk]

/approval request Fixes a critical JVM crash from a race condition when posting dynamic_code_generated JVMTI events.

The patch required manual conflict resolution in JvmtiExport.cpp because JvmtiThreadState::state_for() was previously refactored in this branch. The new regression test, DynamicCodeGeneratedTest, required the removal of an unsupported jtreg tag and was verified to fail without the patch and pass with it.

This fix has been stable in mainline since June 2021. The risk is low, as the fix is a minimal, defensive check.

[openjdk]

@krk
8212155: The approval request has been created successfully.