8369991: Thread blocking during JFR emergency dump must be in safepoint safe state

[mgronlun]

Greetings,

A tiny adjustment to the fix in https://bugs.openjdk.org/browse/JDK-8369255.

A JavaThread must be in a safe safepoint state before taking an infinite nap; for convenience, it goes to _thread_in_native.

Testing: jdk_jfr

Thanks
Markus

---

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

Issue

• JDK-8369991: Thread blocking during JFR emergency dump must be in safepoint safe state (Bug - P3)

Reviewers

• Francesco Andreuzzi (@fandreuz - Author)
• Erik Gahlin (@egahlin - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27862/head:pull/27862
$ git checkout pull/27862

Update a local copy of the PR:
$ git checkout pull/27862
$ git pull https://git.openjdk.org/jdk.git pull/27862/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27862

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27862.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back mgronlun! 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]

@mgronlun This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8369991: Thread blocking during JFR emergency dump must be in safepoint safe state

Reviewed-by: fandreuzzi, egahlin

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 106 new commits pushed to the master branch:

• 92e380c: 8361451: Test vmTestbase/metaspace/stressHierarchy/stressHierarchy012/TestDescription.java fails with OutOfMemoryError: Metaspace
• 65b3239: 8370242: JFR: Clear event reference eagerly when using EventStream
• cbbb0a8: 8367976: Validate and clamp jdk.httpclient.bufsize
• ... and 103 more: https://git.openjdk.org/jdk/compare/b5b83247da9caea30c88b69543e350783663bc46...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@mgronlun The following label will be automatically applied to this pull request:

• hotspot-jfr

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 01: Full - Incremental (c4295b8b)
• 00: Full (1058e7b5)

[mgronlun]

/integrate

[openjdk]

Going to push as commit afba636.
Since your change was applied there have been 106 commits pushed to the master branch:

• 92e380c: 8361451: Test vmTestbase/metaspace/stressHierarchy/stressHierarchy012/TestDescription.java fails with OutOfMemoryError: Metaspace
• 65b3239: 8370242: JFR: Clear event reference eagerly when using EventStream
• cbbb0a8: 8367976: Validate and clamp jdk.httpclient.bufsize
• ... and 103 more: https://git.openjdk.org/jdk/compare/b5b83247da9caea30c88b69543e350783663bc46...master

Your commit was automatically rebased without conflicts.

[openjdk]

@mgronlun Pushed as commit afba636.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.