-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8361614: Missing sub-int value validation in the Class-File API #26201
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
Conversation
👋 Welcome back liach! A progress list of the required criteria for merging this PR into |
@liach 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:
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 4 new commits pushed to the
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 |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice summary fix of the validation.
@liach This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
/touch |
@liach The pull request is being re-evaluated and the inactivity timeout has been reset. |
src/java.base/share/classes/java/lang/classfile/attribute/ModuleExportInfo.java
Outdated
Show resolved
Hide resolved
Thanks for the reviews! /integrate |
Going to push as commit ae9607725c8c6a1b2f2728dbb5f7993722497da7.
Your commit was automatically rebased without conflicts. |
In the
class
file format, a lot of the values areu1
oru2
; the Class-File API consistently model them withint
. However, the API does not, in general, validate that int values passed to the factory methods are not out of the bounds as defined in the class file format. This patch proposes to add such validation for factory methods accepting such more narrow data, prepared by examining allint
-accepting methods in the Class-File API.I expect this to have a small compatibility impact - besides the -1 for the minor version, there is no other places where most significant bits are ever meaningful, and I special cased it and consistently fail fast for all other OOB values, which always mean programmer errors.
A CSR will be created soon as well.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26201/head:pull/26201
$ git checkout pull/26201
Update a local copy of the PR:
$ git checkout pull/26201
$ git pull https://git.openjdk.org/jdk.git pull/26201/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26201
View PR using the GUI difftool:
$ git pr show -t 26201
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26201.diff
Using Webrev
Link to Webrev Comment