-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-19744. Do not use SecurityManager in SubjectUtil.checkThreadInheritsSubject #8088
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
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
The build failures are caused by some kind of JS repo outage. |
steveloughran
left a comment
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.
+1
checkstyle is complaining because you could just go
return JAVA_SPEC_VER <= 21;
but the structure here lines up for options of changing it in future (unlikely, I know)
Ah, true. |
Description of PR
Remove SecurityManager dependent logic for determining if we can optimize out the doAs()/callAs() methods in
SubjectInheritingThread and Daemon on JDK 22 and 23, and assume that we cannot optimize them out.
How was this patch tested?
Ran TestSubjectPropagation with Java 17,21,23,24,25.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?