Skip to content

Conversation

@gerard-ziemski
Copy link

@gerard-ziemski gerard-ziemski commented May 19, 2025

To help with debugging NMT we added more info when an assert gets triggered, but we used tty, which is involved with locks and unfortunately it triggered:

# Internal Error (.../open/src/hotspot/share/runtime/mutex.cpp:457), pid=1088443, tid=1088520
# assert(false) failed: Attempting to acquire lock tty_lock/tty out of order with lock NmtVirtualMemory_lock/service-4 -- possible deadlock

We avoid this, by printing using UL instead of using tty directly.


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-8356233: NMT: tty->print_cr should not be used in VirtualMemoryTracker::add_reserved_region() (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25308

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 19, 2025

👋 Welcome back gziemski! 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
Copy link

openjdk bot commented May 19, 2025

@gerard-ziemski 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:

8356233: NMT: tty->print_cr should not be used in VirtualMemoryTracker::add_reserved_region()

Reviewed-by: jsjolen, dholmes

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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
Copy link

openjdk bot commented May 19, 2025

@gerard-ziemski The following label will be automatically applied to this pull request:

  • hotspot-runtime

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.

@openjdk openjdk bot added the hotspot-runtime hotspot-runtime-dev@openjdk.org label May 19, 2025
@gerard-ziemski gerard-ziemski marked this pull request as ready for review May 19, 2025 20:19
@openjdk openjdk bot added the rfr Pull request is ready for review label May 19, 2025
@mlbridge
Copy link

mlbridge bot commented May 19, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 20, 2025
Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall conversion looks good. If there is no chance of UL using NMT in a way that leads to VMT then this is fine.

Please fix the tag->unsigned->tag code.

Thanks

@gerard-ziemski
Copy link
Author

Thank you Johan and David for your feedback!

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label May 20, 2025
Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Thanks

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 20, 2025
Copy link
Contributor

@jdksjolen jdksjolen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gerard-ziemski
Copy link
Author

/integrate

@openjdk
Copy link

openjdk bot commented May 28, 2025

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 28, 2025
@openjdk openjdk bot closed this May 28, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels May 28, 2025
@openjdk
Copy link

openjdk bot commented May 28, 2025

@gerard-ziemski Pushed as commit 28f5093.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-runtime hotspot-runtime-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants