RFR: 8304425: ClassHierarchyResolver from Reflection [v8]

[Chen Liang]

On Fri, 2 Jun 2023 03:36:35 GMT, Chen Liang <liach at openjdk.org> wrote:

>> Add API to explore Class Hierarchy with a `ClassLoader` or a `Lookup` with proper privileges, with tests.
>> 
>> This addition is useful in case classes at runtime are not loaded from the system class loader, such as Proxy. This is also useful to APIs that generate bytecode with a `Lookup` object, such as a custom single-abstract-method class implementations from a method handle.
>> 
>> See https://mail.openjdk.org/pipermail/classfile-api-dev/2023-March/000249.html as well.
>> 
>> Current questions, which I wish to discuss with @asotona:
>> 1. Should the resolver fail fast on `IllegalAccessException` from the lookup? This usually indicates the hierarchy resolver is set up improperly, and proceeding may simply yield verification errors in class loading that are hard to track. For bytecode-generating APIs, throwing access errors for the Lookup eagerly is also more preferable than later silent generation failure.
>> 2. Whether the default resolver should be reading from jrt alone, reflection alone, or jrt then reflection. I personally believe reflection alone is more reliable, for classes may redefined with instrumentation or jfr, which may not be reflected in the system resources.
>> 3. In addition, I don't think chaining system class loader reflection after system resource retrieval is really meaningful: is there any case where reflection always works while the system resource retrieval always fails?
>
> Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 12 commits:
> 
>  - 1. Moved the default resolver to a static method, in anticipation of future changes
>    2. Removed SecurityManager related content
>    3. Changed ClassHierarchyInfo into an interface
>    4. Moved caching method from static to instance method
>  - Merge branch 'master' into hierarchy-resolve
>  - rename to ofClassLoading/ofResourceParsing
>    convert the default class provider to bypass security manager restrictions
>  - Merge branch 'master' into hierarchy-resolve
>  - Merge branch 'master' into hierarchy-resolve
>  - Test both cached and uncached resolvers
>  - Update the class hierarchy resolver api as per mailing list last week
>  - Merge branch 'master' into hierarchy-resolve
>  - Update src/java.base/share/classes/jdk/internal/classfile/impl/ClassHierarchyImpl.java
>    
>    Co-authored-by: Andrey Turbanov <turbanoff at gmail.com>
>  - Make lookup based resolver throw on illegal access eagerly
>  - ... and 2 more: https://git.openjdk.org/jdk/compare/101bf229...9e9079fb

A brief summary of the latest update:
1. I've moved to implement all 3 API changes to ClassHierarchyResolver discussed on classfile-api-dev
2. I've dropped SecurityManager content; if they are needed by another patch, those patches can add on their own.

This will be in conflict with the Classfile object update; I can update accordingly if that one is integrated first.

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

PR Comment: https://git.openjdk.org/jdk/pull/13082#issuecomment-1573096991