Generating verification metadata and verifying a runtime type based on verification metadata

• US 10,417,024 B2
• Filed: 12/10/2018
• Issued: 09/17/2019
• Est. Priority Date: 03/30/2016
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kinnear, Karen Margaret Pearson, Seigel, Harold David, Foltan, Lois Dickinson, Lam, Ioi Kim
• Primary Examiner(s): Nahar, Qamrun
• Application Number:
  US16/214,580
• Publication Number:
  US 20190108047A1
• Time in Patent Office: Days
• Field of Search: None
• CPC Class Codes: G06F 8/437 Type checking
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

Operations include (a) receiving a request to verify a first runtime type loaded based on a first runtime type reference; (b) identifying verification metadata comprising a stored assignable relationship between a second runtime type reference and a third runtime type reference; (c) determining whether an actual assignable relationship between a second runtime type and a third runtime type adheres to the stored assignable relationship between the second runtime type reference and the third runtime type reference; and (d) responsive at least to determining that the actual assignable relationship adheres to the stored assignable relationship, determining that the first runtime type is verified based on the verification metadata.

Claims

1. One or more non-transitory machine-readable media storing instructions which, when executed by one or more processors, cause:

obtaining a runtime type loaded based on a first runtime type reference during a first runtime;

determining that the runtime type loaded based on the first runtime type reference during the first runtime includes a statement that is associated with a second runtime type reference and a third runtime type reference;

obtaining a runtime type loaded based on the second runtime type reference during the first runtime;

obtaining a runtime type loaded based on the third runtime type reference during the first runtime;

determining that a particular assignable relationship exists between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime;

generating verification metadata, associated with the first runtime type reference, indicating the particular assignable relationship associated with (a) the second runtime type reference and (b) the third runtime type reference;

wherein a verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during a second runtime requires that an actual assignable relationship between a runtime type loaded based on the second runtime type reference during the second runtime and a runtime type loaded based on the third runtime type reference during the second runtime adheres to the particular assignable relationship associated with the second runtime type reference and the third runtime type reference indicated by the verification metadata.

2. The one or more media of claim 1, further storing instructions which, when executed by one or more processors, cause:

responsive to determining that the verification constraint is satisfied with respect to the runtime type loaded based on the first runtime type reference during the second runtime;

determining that the runtime type loaded based on the first runtime type reference during the second runtime is verified based on the verification metadata.

3. The one or more media of claim 2, wherein a first number of intermediate sub-types in a first inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime, and a second number of intermediate sub-types in a second inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the second runtime and (b) the runtime type loaded based on the third runtime type reference during the second runtime, are different.

4. The one or more media of claim 2, wherein:

determining that the runtime type loaded based on the first runtime type reference during the first runtime is verified comprises;

verifying a static constraint with respect to the runtime type loaded based on the first runtime type reference during the first runtime;

determining that the runtime type loaded based on the first runtime type reference during the second runtime is verified comprises;

determining that the verification constraint indicated by the verification metadata is satisfied, without examining the static constraint with respect to the runtime type loaded based on the first runtime type reference during the second runtime.

5. The one or more media of claim 1, wherein the first runtime type reference comprises (a) a first type reference and (b) a defining class loader type reference.

6. The one or more media of claim 1, wherein the verification metadata further comprises one or more of:

(a) a checksum of a class file corresponding to the first runtime type reference;

(b) a size of the class file corresponding to the first runtime type reference;

(c) a timestamp associated with the class file corresponding to the first runtime type reference; and

(d) a location identifier associated with the class file corresponding to the first runtime type reference.

7. The one or more media of claim 1, wherein the verification metadata is associated with a plurality of runtime type references, including the first runtime type reference, and the verification metadata indicates a respective set of one or more assignable relationships associated with the plurality of runtime type references.

8. The one or more media of claim 1, further storing instructions which, when executed by one or more processors, cause:

storing the verification metadata and the runtime type loaded based on the first runtime type reference during the second runtime in a runtime image.

9. The one or more media of claim 1, further storing instructions which, when executed by one or more processors, cause:

storing the verification metadata and the runtime type loaded based on the first runtime type reference during the second runtime in an archive.

10. The one or more media of claim 1, further storing instructions which, when executed by one or more processors, cause:

storing the verification metadata and the runtime type loaded based on the first runtime type reference during the second runtime in a machine language image.

11. The one or more media of claim 1, wherein the verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during the second runtime does not require that the actual assignable relationship be same as the particular assignable relationship.

12. The one or more media of claim 1, wherein the verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during the second runtime does not require that the runtime type loaded based on the second runtime type reference during the second runtime be equivalent to the runtime type loaded based on the second runtime type reference during the first runtime.

13. The one or more media of claim 1, wherein the verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during the second runtime does not require that:

a first number of intermediate sub-types in a first inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime, and a second number of intermediate sub-types in a second inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the second runtime and (b) the runtime type loaded based on the third runtime type reference during the second runtime, be the same.

14. The one or more media of claim 1, wherein the particular assignable relationship indicates that the second runtime type reference is a sub-type of the third runtime type reference.

15. A system, comprising:

at least one device including a hardware processor; and

the system being configured to perform operations comprising;

obtaining a runtime type loaded based on a first runtime type reference during a first runtime;

determining that the runtime type loaded based on the first runtime type reference during the first runtime includes a statement that is associated with a second runtime type reference and a third runtime type reference;

obtaining a runtime type loaded based on the second runtime type reference during the first runtime;

obtaining a runtime type loaded based on the third runtime type reference during the first runtime;

determining that a particular assignable relationship exists between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime;

generating verification metadata, associated with the first runtime type reference, indicating the particular assignable relationship associated with (a) the second runtime type reference and (b) the third runtime type reference;

wherein a verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during a second runtime requires that an actual assignable relationship between a runtime type loaded based on the second runtime type reference during the second runtime and a runtime type loaded based on the third runtime type reference during the second runtime adheres to the particular assignable relationship associated with the second runtime type reference and the third runtime type reference indicated by the verification metadata.

16. The system of claim 15, wherein the operations further comprise:

responsive to determining that the verification constraint is satisfied with respect to the runtime type loaded based on the first runtime type reference during the second runtime;

determining that the runtime type loaded based on the first runtime type reference during the second runtime is verified based on the verification metadata.

17. The system of claim 16, wherein a first number of intermediate sub-types in a first inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime, and a second number of intermediate sub-types in a second inheritance chain between (a) the runtime type loaded based on the second runtime type reference during the second runtime and (b) the runtime type loaded based on the third runtime type reference during the second runtime, are different.

18. The system of claim 16, wherein:

determining that the runtime type loaded based on the first runtime type reference during the first runtime is verified comprises;

verifying a static constraint with respect to the runtime type loaded based on the first runtime type reference during the first runtime;

determining that the runtime type loaded based on the first runtime type reference during the second runtime is verified comprises;

determining that the verification constraint indicated by the verification metadata is satisfied, without examining the static constraint with respect to the runtime type loaded based on the first runtime type reference during the second runtime.

19. The system of claim 16, further storing instructions which, when executed by one or more processors, cause:

storing the verification metadata and the runtime type loaded based on the first runtime type reference during the second runtime in a runtime image.

20. A method, comprising:

obtaining a runtime type loaded based on a first runtime type reference during a first runtime;

determining that the runtime type loaded based on the first runtime type reference during the first runtime includes a statement that is associated with a second runtime type reference and a third runtime type reference;

obtaining a runtime type loaded based on the second runtime type reference during the first runtime;

obtaining a runtime type loaded based on the third runtime type reference during the first runtime;

determining that a particular assignable relationship exists between (a) the runtime type loaded based on the second runtime type reference during the first runtime and (b) the runtime type loaded based on the third runtime type reference during the first runtime;

generating verification metadata, associated with the first runtime type reference, indicating the particular assignable relationship associated with (a) the second runtime type reference and (b) the third runtime type reference;

wherein a verification constraint for using the verification metadata to verify a runtime type loaded based on the first runtime type reference during a second runtime requires that an actual assignable relationship between a runtime type loaded based on the second runtime type reference during the second runtime and a runtime type loaded based on the third runtime type reference during the second runtime adheres to the particular assignable relationship associated with the second runtime type reference and the third runtime type reference indicated by the verification metadata;

wherein the method is performed by at least one device including a hardware processor.