Skip to content

8341020: Error handler crashes when Metaspace is not fully initialized #21206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

shipilev
Copy link
Member

@shipilev shipilev commented Sep 26, 2024

When debugging CDS, I asked for os::print_location when Metaspace was not completely initialized. I suspect the same might happen if error handler fires very early in startup sequence.

os::print_location got to Metaspace::contains, which ended up in Metaspace::is_in_nonclass_metaspace, which crashed, since VirtualSpaceList was null. Other checks in Metaspace::contains seem to only check the address against the boundaries, and are not affected.

Additional testing:

  • The same debugging session did not crash the VM after the patch

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-8341020: Error handler crashes when Metaspace is not fully initialized (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 21206

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 26, 2024

👋 Welcome back shade! 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 Sep 26, 2024

@shipilev 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:

8341020: Error handler crashes when Metaspace is not fully initialized

Reviewed-by: kbarrett, jsjolen, stefank, 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 9 new commits pushed to the master branch:

  • 40a44e1: 8340851: Open some TextArea awt tests
  • b993227: 8342119: Shenandoah: Remove extra ShenandoahUpdateRefsClosure
  • 83e9e48: 8325937: runtime/handshake/HandshakeDirectTest.java causes "monitor end should be strictly below the frame pointer" assertion failure on AArch64
  • 236c71c: 8341376: Open some TextArea awt tests 4
  • 979895d: 8342079: Shenandoah: Remove extra ShenandoahInitMarkRootsClosure
  • 9a94884: 8341055: Open some TextArea awt tests 2
  • 7e98f59: 8340987: Open some TextArea awt tests 1
  • d915ac2: 8339871: serviceability/sa/TestDebugInfoDecode.java should be driver
  • 363327e: 8341452: Test runtime/cds/appcds/DumpRuntimeClassesTest.java from JDK-8324259 is failing

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 openjdk bot added the rfr Pull request is ready for review label Sep 26, 2024
@openjdk
Copy link

openjdk bot commented Sep 26, 2024

@shipilev 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 Sep 26, 2024
@mlbridge
Copy link

mlbridge bot commented Sep 26, 2024

Webrevs

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 Sep 29, 2024
@@ -992,6 +992,7 @@ bool Metaspace::is_in_shared_metaspace(const void* ptr) {

// Returns true if pointer points into one of the non-class-space metaspace regions.
bool Metaspace::is_in_nonclass_metaspace(const void* ptr) {
return VirtualSpaceList::vslist_nonclass()->contains((MetaWord*)ptr);
VirtualSpaceList* list = VirtualSpaceList::vslist_nonclass();
return (list != nullptr) && list->contains((MetaWord*) ptr);

Choose a reason for hiding this comment

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

I'm not sure about this. This, and a number of other related functions nearby,
all seem like they should have Metaspace::initialized() as a precondition. And
the call to Metaspace::contains in os::print_location should be conditional on
Metaspace::initialized(). (There may be other "is initialized" checks that
should be made by (and offered to) os::print_location, but that's beyond the
scope of this change.)

Copy link
Member

Choose a reason for hiding this comment

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

FWIW, we had a similar discussion in #19435.

Copy link
Contributor

Choose a reason for hiding this comment

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

All of these methods are public. I think that it seems sane to assume that they are the boundary for checking whether Metaspace is initialized before doing something.

Copy link
Member Author

Choose a reason for hiding this comment

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

All right, I think checking for Metaspace::initialized() in os::print_location is more in line with other changes, notably JDK-8333290. This is Kim's suggestion, I think. So I did just that.

@shipilev shipilev changed the title 8341020: Metaspace::contains crashes when Metaspace is not fully initialized 8341020: Error handler crashes when Metaspace is not fully initialized Oct 17, 2024
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Oct 17, 2024
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.

Thanks, this looks good to me.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 17, 2024
Copy link
Member

@stefank stefank left a comment

Choose a reason for hiding this comment

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

Looks good to me.

Copy link

@kimbarrett kimbarrett left a comment

Choose a reason for hiding this comment

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

Looks good.

@shipilev
Copy link
Member Author

Thank you!

/integrate

@openjdk
Copy link

openjdk bot commented Oct 18, 2024

Going to push as commit 7f4ed50.
Since your change was applied there have been 17 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 Oct 18, 2024
@openjdk openjdk bot closed this Oct 18, 2024
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 18, 2024
@openjdk
Copy link

openjdk bot commented Oct 18, 2024

@shipilev Pushed as commit 7f4ed50.

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

@shipilev shipilev deleted the JDK-8341020-metaspace-crash branch January 8, 2025 12:38
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.

5 participants