Shared library loading using predefined loading policy
A computer-implemented process is disclosed. An application is loaded into a local address space. A request by the application to load a target shared library is intercepted by an interceptor. Using the interceptor and based upon the request being intercepted, a shared library correlation table is searched for a loading count and a loading policy associated with the target shared library. Based upon the loading count and the loading policy, a selection is made between loading the target shared library as a shared library container, and loading the target shared library into the local address space. The target shared library is loaded based upon the selecting. The loading count represents a number of times the target shared library was loaded, and the loading policy indicates how the target shared library is to be loaded.
1 . A computer-implemented method, comprising:
loading an application into a local address space;
intercepting, by an interceptor, a request by the application to load a target shared library, wherein the request is generated using a dlopen call;
searching, using the interceptor and based upon the request being intercepted, a shared library correlation table for a loading count and a loading policy associated with the target shared library;
selecting, based upon the loading count and the loading policy, between:
loading the target shared library as a shared library container, and
loading the target shared library into the local address space; and
loading the target shared library based upon the selecting, wherein
the loading count represents a number of times the target shared library was loaded,
the loading policy indicates how the target shared library is to be loaded,
the loading of the target shared library is performed using a mocked dlopen function, and
the mocked dlopen function includes the searching the shared library correlation table.
2 . The computer-implemented method of claim 1 , wherein
the shared library correlation table includes, for each target shared library of a plurality of target shared libraries:
the loading count,
the loading policy, and
one of a local handle or a container ID,
the local handle is associated with a pointer to the target shared library loaded in the local address space, and
the container ID is an identification of the shared library container of the target shared library.
3 . The computer-implemented method of claim 2 , wherein upon the interceptor intercepting a request to unload the target shared library, one of the local handle or the container ID for the target shared library is retrieved by the interceptor from the shared library correlation table.
4 . The computer-implemented method of claim 3 , wherein the interceptor is configured, based on the local handle being retrieved, to forward the local handle to a dynamic linker to unload the target shared library from the local address space.
5 . The computer-implemented method of claim 3 , wherein the interceptor is configured, based upon the container ID being retrieved, to forward the container ID to a container handler to unload the target shared library.
6 . The computer-implemented method of claim 1 , wherein
based upon the loading count being an initial value:
a dynamic linker is invoked to load the target shared library,
the loading count is incremented to generate an incremented loading count, and
the incremented loading count is stored within the shared library correlation table.
7 . The computer-implemented method of claim 1 , further comprising
invoking, based upon the loading count being greater than an initial value and the loading policy indicates to load the target shared library as a container, a container platform to load the shared library container.
8 . A computer hardware system, comprising:
a hardware processor configured to perform the following executable operations:
loading an application into a local address space;
intercepting, by an interceptor, a request by the application to load a target shared library, wherein the request is generated using a dlopen call;
searching, using the interceptor and based upon the request being intercepted, shared library correlation table for a loading count and a loading policy associated with the target shared library;
selecting, based upon the loading count and the loading policy, between:
loading the target shared library as a shared library container, and
loading the target shared library into the local address space; and
loading the target shared library based upon the selecting, wherein
the loading count represents a number of times the target shared library was loaded,
the loading policy indicates how the target shared library is to be loaded,
the loading of the target shared library is performed using a mocked dlopen function, and
the mocked dlopen function includes the searching the shared library correlation table.
9 . The computer hardware system of claim 8 , wherein
the shared library correlation table includes, for each target shared library of a plurality of target shared libraries:
the loading count,
the loading policy, and
one of a local handle or a container ID,
the local handle is associated with a pointer to the target shared library loaded in the local address space, and
the container ID is an identification of the shared library container of the target shared library.
10 . The computer hardware system of claim 9 , wherein upon the interceptor intercepting a request to unload the target shared library, one of the local handle or the container ID for the target shared library is retrieved by the interceptor from the shared library correlation table.
11 . The computer hardware system of claim 10 , wherein the interceptor is configured, based on the local handle being retrieved, to forward the local handle to a dynamic linker to unload the target shared library from the local address space.
12 . The computer hardware system of claim 10 , wherein
the interceptor is configured, based upon the container ID being retrieved, to forward the container ID to a container handler to unload the target shared library.
13 . The computer hardware system of claim 8 , wherein
based upon the loading count being an initial value:
a dynamic linker is invoked to load the target shared library,
the loading count is incremented to generate an incremented loading count, and
the incremented loading count is stored within the shared library correlation table.
14 . The computer hardware system of claim 8 , wherein the hardware processor is further configured to perform the operations comprising:
invoking, based upon the loading count being greater than an initial value and the loading policy that indicates to load the target shared library as a container, a container platform to load the shared library container.
15 . A computer program product, comprising:
a computer readable storage medium having stored therein program code for training a training dataset,
the program code, which when executed by a computer hardware system, cause the computer hardware system to perform:
loading an application into a local address space;
intercepting, by an interceptor, a request by the application to load a target shared library, wherein the request is generated using a dlopen call;
searching, using the interceptor and based upon the request being intercepted, a shared library correlation table for a loading count and a loading policy associated with the target shared library;
selecting, based upon the loading count and the loading policy, between:
loading the target shared library as a shared library container, and
loading the target shared library into the local address space; and
loading the target shared library based upon the selecting, wherein
the loading count represents a number of times the target shared library was loaded,
the loading policy indicates how the target shared library is to be loaded,
the loading of the target shared library is performed using a mocked dlopen function, and
the mocked dlopen function includes the searching of the shared library correlation table.
16 . The computer program product of claim 15 , wherein
the shared library correlation table includes, for each target shared library of a plurality of target shared libraries:
the loading count,
the loading policy, and
one of a local handle or a container ID,
the local handle is associated with a pointer to the target shared library loaded in the local address space, and
the container ID is an identification of the shared library container of the target shared library.
17 . The computer program product of claim 16 , wherein upon the interceptor intercepting a request to unload the target shared library, one of the local handle or the container ID for the target shared library is retrieved by the interceptor from the shared library correlation table.
18 . The computer program product of claim 15 , wherein based upon the loading count being an initial value,
a dynamic linker is invoked to load the target shared library,
the loading count is incremented to generate an incremented loading count, and
the incremented loading count is stored within the shared library correlation table.