Skip to content

Conversation

@matias9927
Copy link
Contributor

@matias9927 matias9927 commented Oct 3, 2024


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-8341444: Unnecessary check for JSRs in CDS (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 21330

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 3, 2024

👋 Welcome back matsaave! 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 Oct 3, 2024

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

8341444: Unnecessary check for JSRs in CDS

Reviewed-by: dholmes, coleenp

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 359 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
Copy link

openjdk bot commented Oct 3, 2024

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

  • hotspot

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 hotspot-dev@openjdk.org label Oct 3, 2024
@matias9927 matias9927 marked this pull request as ready for review October 3, 2024 20:12
@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 3, 2024
@mlbridge
Copy link

mlbridge bot commented Oct 3, 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.

Again apologies for commenting and running off on vacation, but this one does not look right to me based on the description.

if (len == 0) len = Bytecodes::length_at(_method(), bcp);
if (len <= 0 || (_bci > _end_bci - len) || (_bci - len >= _next_bci)) {
raw_code = code = Bytecodes::_illegal;
fatal("Should have been caught by verifier");
Copy link
Member

Choose a reason for hiding this comment

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

Verification may be disabled, This may be a risky change in behaviour.

Copy link
Contributor

Choose a reason for hiding this comment

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

If verification is disabled, this fatal is better than what might come next. But there may be callers now or in the future that check for Bytecodes::_illegal, so I don't think we should have this assert even though we don't have any code that hits it.

Comment on lines 2458 to 2459
// don't have any methods share the Universe::_the_empty_method_array which is in the RO region.
if (_methods != nullptr && _methods->length() > 0 &&
!can_be_verified_at_dumptime() && methods_contain_jsr_bytecode()) {
if (_methods != nullptr && _methods->length() > 0 && !can_be_verified_at_dumptime()) {
// To handle jsr bytecode, new Method* maybe stored into _methods
Copy link
Member

Choose a reason for hiding this comment

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

Based on the comment we only need to do this if the method does contain a JSR bytecode - now we will do it for all cases where verification can't be done at dumptime. ??

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, we will put these in RW space the time. Using the BytecodeStream to look for JSRs in unverified code is risky, so we avoid doing this optimization.

Copy link
Member

Choose a reason for hiding this comment

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

So shouldn't the comment be updated to indicate that we cannot safely check if the jsr bytecode exists and so all methods that can't be verified are made writeable?

Copy link
Contributor

@coleenp coleenp left a comment

Choose a reason for hiding this comment

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

I think you should take out the 'fatal' error in bytecodeStream.

if (len == 0) len = Bytecodes::length_at(_method(), bcp);
if (len <= 0 || (_bci > _end_bci - len) || (_bci - len >= _next_bci)) {
raw_code = code = Bytecodes::_illegal;
fatal("Should have been caught by verifier");
Copy link
Contributor

Choose a reason for hiding this comment

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

If verification is disabled, this fatal is better than what might come next. But there may be callers now or in the future that check for Bytecodes::_illegal, so I don't think we should have this assert even though we don't have any code that hits it.

Comment on lines 2458 to 2459
// don't have any methods share the Universe::_the_empty_method_array which is in the RO region.
if (_methods != nullptr && _methods->length() > 0 &&
!can_be_verified_at_dumptime() && methods_contain_jsr_bytecode()) {
if (_methods != nullptr && _methods->length() > 0 && !can_be_verified_at_dumptime()) {
// To handle jsr bytecode, new Method* maybe stored into _methods
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, we will put these in RW space the time. Using the BytecodeStream to look for JSRs in unverified code is risky, so we avoid doing this optimization.

Copy link
Contributor

@coleenp coleenp left a comment

Choose a reason for hiding this comment

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

This looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 14, 2024
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Oct 17, 2024
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.

Thank you!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 18, 2024
@matias9927
Copy link
Contributor Author

Thanks for the reviews @dholmes-ora and @coleenp!
/integrate

@openjdk
Copy link

openjdk bot commented Oct 18, 2024

Going to push as commit 28252bb.
Since your change was applied there have been 365 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

@matias9927 Pushed as commit 28252bb.

💡 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 hotspot-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants