-
Notifications
You must be signed in to change notification settings - Fork 17
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
Wrap a call to QatZipper with AccessController.doPrivileged. #211
Wrap a call to QatZipper with AccessController.doPrivileged. #211
Conversation
Signed-off-by: Ubuntu <[email protected]> Signed-off-by: Mulugeta Mammo <[email protected]>
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.
@mulugetam this permission in general should never be granted (especially, in case of codecs), and usually indicates the issue in other places (caller site). I believe you have to wrap the call into AccessController.doPriveledged instead
@reta will do that. |
Signed-off-by: Mulugeta Mammo <[email protected]>
Thanks @mulugetam , I see the failing CI check, will fix it first thing tomorrow (if you have an opportunity, please apply the changes from opensearch-project/ml-commons#3223, thank you) |
@mulugetam could you please rebase? thank you! |
Signed-off-by: Andriy Redko <[email protected]>
Just did. Thank you @reta |
env: | ||
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true | ||
|
||
options: ${{ needs.Get-CI-Image-Tag.outputs.ci-image-start-options }} |
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.
Interesting, this change is in main
already ...
* Grant qat-java a permission to modify arbitrary thread. Signed-off-by: Ubuntu <[email protected]> Signed-off-by: Mulugeta Mammo <[email protected]> * Wrap a QatZipper() inside AccessController.doPrivileged(). Signed-off-by: Mulugeta Mammo <[email protected]> * Fix GitHib action workflows (#212) Signed-off-by: Andriy Redko <[email protected]> --------- Signed-off-by: Ubuntu <[email protected]> Signed-off-by: Mulugeta Mammo <[email protected]> Signed-off-by: Andriy Redko <[email protected]> Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Andriy Redko <[email protected]> (cherry picked from commit 9de7fd3) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…214) * Grant qat-java a permission to modify arbitrary thread. * Wrap a QatZipper() inside AccessController.doPrivileged(). * Fix GitHib action workflows (#212) --------- (cherry picked from commit 9de7fd3) Signed-off-by: Ubuntu <[email protected]> Signed-off-by: Mulugeta Mammo <[email protected]> Signed-off-by: Andriy Redko <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Andriy Redko <[email protected]>
A customer reached out to inform us that they were unable to use
qat_deflate
andqat_lz4
. Upon investigation, I discovered thatisQATAvailable()
was returningfalse
due to ajava.security
permission fail in here. This behavior is unexpected, as my initial PR did not require it (as far as I can remember).This PR addresses the issue by adding the necessary permission to the
qat-java
codebase.@sarthakaggarwal97
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.