-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8309727: Assert privileges while reading the jdk.incubator.vector.VECTOR_ACCESS_OOB_CHECK system property #14392
Conversation
👋 Welcome back chegar! A progress list of the required criteria for merging this PR into |
@@ -28,6 +28,8 @@ | |||
/** | |||
* @test | |||
* @modules jdk.incubator.vector | |||
* @run main VectorRuns | |||
* @run main/othervm/java.security.policy=empty_security.policy VectorRuns |
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.
I just added a minimal test here, so as not to otherwise disturb other areas. This is sufficient to very the fix, and ensure that it does not reoccur.
@@ -68,7 +70,7 @@ static int countRunAscendingVector(int[] a) { | |||
if (r >= a.length) | |||
return a.length; | |||
|
|||
int length = a.length & (species.length() - 1); | |||
int length = a.length & ~(species.length() - 1); |
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.
pre existing test issue.
@ChrisHegarty To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
/label core-libs |
@ChrisHegarty |
@PaulSandoz We just ran into this yesterday, elastic/elasticsearch#96715. The change here is trivial. |
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.
Looks good
@ChrisHegarty 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 17 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 |
Thanks @ChrisHegarty for fixing. Lucene's tests didn't find this, unfortunately! |
Here is our Lucene workaround: apache/lucene#12362 |
/integrate |
Going to push as commit cee5724.
Your commit was automatically rebased without conflicts. |
@ChrisHegarty Pushed as commit cee5724. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
A trivial use of the Vector API when run with the security manager and a domain that does not grant permissions fails with java.security.AccessControlException: access denied ("java.util.PropertyPermission" "jdk.incubator.vector.VECTOR_ACCESS_OOB_CHECK" "read").
The fix it minimal, as consistent with other system property access in the JDK - just access the property while asserting privileged. Note: no explicit permission grant to the vector module is required, as it is in the boot loader.
This is the only such security manager related issue I see in this code, and I have looked.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14392/head:pull/14392
$ git checkout pull/14392
Update a local copy of the PR:
$ git checkout pull/14392
$ git pull https://git.openjdk.org/jdk.git pull/14392/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14392
View PR using the GUI difftool:
$ git pr show -t 14392
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14392.diff
Webrev
Link to Webrev Comment