RFR: 8195744: Avoid calling ClassLoader.checkPackageAccess if security manager is not installed

Coleen Phillimore coleenp at openjdk.java.net
Thu Feb 4 19:17:55 UTC 2021


This change does not call up to Java for checkPackageAccess if the security manager is NULL, but still saves the protection domain in the pd_set for that dictionary entry.  If the option -Djava.security.manager=disallow is set, that means that there will never be a security manager and the JVM code can avoid saving the protection domains completely. 
See the two functions java_lang_System::has_security_manager() and java_lang_System::allow_security_manager() for details.
Also deleted ProtectionDomainVerification because there's no use for this option.

Tested with tier1 hotspot, jdk and langtools.
and tier2-6.

-------------

Commit messages:
 - 8195744: Avoid calling ClassLoader.checkPackageAccess if security manager is not installed

Changes: https://git.openjdk.java.net/jdk/pull/2410/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=2410&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8195744
  Stats: 144 lines in 8 files changed: 72 ins; 33 del; 39 mod
  Patch: https://git.openjdk.java.net/jdk/pull/2410.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/2410/head:pull/2410

PR: https://git.openjdk.java.net/jdk/pull/2410


More information about the hotspot-runtime-dev mailing list