Skip to content

Conversation

@vy
Copy link
Contributor

@vy vy commented May 30, 2025

Reverts certain JDK-8353197 (which implements JavaDoc improvement and precautionary naming for certain unsafe methods in jdk.internal.access.JavaLangAccess) changes that are found to be incorrect. See the JBS issue for details on the followed evaluation process.


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-8357821: Revert incorrectly named JavaLangAccess::unchecked* methods (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25545

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 30, 2025

👋 Welcome back vyazici! 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 30, 2025

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

8357821: Revert incorrectly named JavaLangAccess::unchecked* methods

Reviewed-by: pminborg

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 155 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 rfr Pull request is ready for review label May 30, 2025
@openjdk
Copy link

openjdk bot commented May 30, 2025

@vy The following labels will be automatically applied to this pull request:

  • core-libs
  • nio
  • security

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

@openjdk openjdk bot added security security-dev@openjdk.org nio nio-dev@openjdk.org core-libs core-libs-dev@openjdk.org labels May 30, 2025
@mlbridge
Copy link

mlbridge bot commented May 30, 2025

Webrevs

@wangweij
Copy link
Contributor

/label remove security

@openjdk openjdk bot removed the security security-dev@openjdk.org label May 30, 2025
@openjdk
Copy link

openjdk bot commented May 30, 2025

@wangweij
The security label was successfully removed.

@minborg
Copy link
Contributor

minborg commented Jun 2, 2025

The changes look good to me. I wonder if we should add that implementations of the affected method shall do bounds checking to reduce the likelihood of a new/updated native implementation miss that?

@vy
Copy link
Contributor Author

vy commented Jun 3, 2025

I wonder if we should add that implementations of the affected method shall do bounds checking to reduce the likelihood of a new/updated native implementation miss that?

@minborg, would you mind elaborating on this a bit, please? Do you imply adding an @implSpec to the touched JavaLangAccess methods?

@minborg
Copy link
Contributor

minborg commented Jun 4, 2025

I wonder if we should add that implementations of the affected method shall do bounds checking to reduce the likelihood of a new/updated native implementation miss that?

@minborg, would you mind elaborating on this a bit, please? Do you imply adding an @implSpec to the touched JavaLangAccess methods?

Yes, I think that would be a good thing to do.

@vy
Copy link
Contributor Author

vy commented Jun 5, 2025

@minborg, added @implSpec in 1e13559.

Copy link
Contributor

@minborg minborg left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you for these updates!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 5, 2025
@vy
Copy link
Contributor Author

vy commented Jun 6, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Jun 6, 2025

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

openjdk bot commented Jun 6, 2025

@vy Pushed as commit e918a59.

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

@vy vy deleted the jlaRevert branch June 6, 2025 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated nio nio-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants