Skip to content
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

8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache #9724

Conversation

tschatzl
Copy link
Contributor

@tschatzl tschatzl commented Aug 3, 2022

Hi all,

can I have reviews for this wrong use of G1CollectedHeap::heap_region_containing in G1RemSet::clean_card_before_refine()?

If a card is evicted from the hot card cache it might also be located in an outdated (reclaimed) region (by Remark). So the call needs to explicitly consider that case and use heap_region_containing_or_null and appropriately check for that later.

This is only an issue in debug mode, because while still this is kind of an illegal request, the return value will always be a valid HeapRegion instance as we never deallocate them.

Testing: reproduced crashes with the given test case (1:5), no more crashes afterwards.

Thanks,
Thomas


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-8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 9724

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

Using diff file

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

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 3, 2022

👋 Welcome back tschatzl! 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 openjdk bot changed the title 8291653 8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache Aug 3, 2022
@openjdk
Copy link

openjdk bot commented Aug 3, 2022

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

  • hotspot-gc

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-gc hotspot-gc-dev@openjdk.org label Aug 3, 2022
@tschatzl tschatzl marked this pull request as ready for review August 3, 2022 12:23
@openjdk openjdk bot added the rfr Pull request is ready for review label Aug 3, 2022
@mlbridge
Copy link

mlbridge bot commented Aug 3, 2022

Webrevs

@dcubed-ojdk
Copy link
Member

It would be good if this PR got reviewed and integrated soon. The number of
sightings of this test failure is starting to show up on my radar and I'll likely
ProblemList it tomorrow (Fri) if the PR is not integrated soon.

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.

@openjdk
Copy link

openjdk bot commented Aug 5, 2022

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

8291653: G1 refinement incorrectly expects always-valid HeapRegion out of the Hot Card Cache

Reviewed-by: kbarrett, ayang

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 43 new commits pushed to 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 ready Pull request is ready to be integrated label Aug 5, 2022
@tschatzl
Copy link
Contributor Author

tschatzl commented Aug 5, 2022

Thanks @albertnetymk @kimbarrett for your reviews
/integrate

@openjdk
Copy link

openjdk bot commented Aug 5, 2022

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

openjdk bot commented Aug 5, 2022

@tschatzl Pushed as commit f9bb367.

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

@tschatzl tschatzl deleted the submit/8291653-hcc-eviction-uncommitted-regions branch August 5, 2022 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants