JPH04291419A - Multi-load module protection system - Google Patents

Abstract

PURPOSE:To evade the deterioration of the system processing ability and to prevent the destruction of an area in a multi-load module protection system by assuring the cooperation between the protectable and unprotectable load modules. CONSTITUTION:A multi-module component load module 1 is provided together with a load module evolving part 5 which evolves collectively the protectable and unprotectable modules included in the modules 1 into a main storage through the protection boundary adjustment and also performs the reresolution of the address constant of each load module. Then the protection is set in the area of a protectable load module which is evolved by the part 5.

Description

[Detailed description of the invention]

0001

[Industrial Field of Application] The present invention is a multiple load module protection method for protecting multiple load modules on main memory, and the present invention is a multiple load module protection method for protecting multiple load modules when they are deployed in the main memory. It concerns the protection method. The hardware protection function cannot be applied to the multi-module configuration load module due to the mix of protectable and unprotectable modules, and the program location in main memory corresponds to low-order addresses. , located in a position susceptible to area destruction. Therefore, the entire program area of the load module may be destroyed at any time due to an error in another program. Therefore, protection (memory protection) is required even for programs configured in this manner.

0002

[Prior Art] Conventionally, the main memory protection area is protected in block units such as page units and segment units. A common idea is to register a dummy module within the group, adjust the protect boundary, and load it into the main memory resident program area. Additionally, as shown in ■ in Figure 4, it is possible to determine the protect range on the main memory based on the unit (size) of the load module expanded to the main memory, and then load the target single load module into that range. Conceivable.

0003

[Problems to be Solved by the Invention] As mentioned above, since it is necessary to determine the protection area in units of protection blocks such as pages and segments, load modules with multiple module configurations can be protected while others are not. It is necessary to separate it into different load modules. However, the load module (main memory resident load module) that exists as part of the core of the OS has close cooperation with the individual load modules within the load module in order to efficiently control the system. There is a problem in determining the address definition defined in the file, which lowers the processing capacity of the related load module, and it is not possible to divide the load module into two types: a protectable load module and a non-protectable load module. In addition, the overall size of the load module, which is the core of the OS, is large and it is located at a relatively low address in main memory, so it is easily affected by area destruction due to malfunction of other programs.
Some protection is required for load modules with multiple module configurations.

[0004] The present invention groups load modules having a plurality of modules into load modules that can be protected and load modules that cannot be protected, performs boundary adjustment, loads them onto main memory, resolves address constants, and sets protection functions. The purpose is to ensure cooperation between protectable load modules and unprotectable load modules, avoid a decline in system processing capacity, and prevent area destruction.

[0005]

[Means for Solving the Problems] FIG. 1 shows a diagram of the principle configuration of the present invention. In FIG. 1, a multi-module configuration load module 1 is one compiled and linked load module consisting of a protectable load module and an unprotectable load module.

[0006] The load module re-editing unit 2 performs a re-edited load process on the load module 1 having a plurality of modules, which is organized into a protectable load module and an unprotectable load module based on the load module re-editing control data 3. Module 4 is generated. At startup, the load module expansion unit 5 extracts the protectable load module and the unprotectable load module from the re-edited load module 4, performs boundary adjustment, expands them onto the main memory, and resolves the address constant of the load module. This is what we do.

[0007]

[Operation] As shown in FIG. 1, in the present invention, the load module re-editing section 2
is re-edited into a protectable module and an unprotectable load module based on the load module re-edit control data 3 to generate a re-edited load module 4, stored in a library, and loaded at startup. The module expansion unit 5 adjusts the boundaries of the protectable load module and unprotectable load module of this re-edited load module 4, expands them into the main memory, and re-resolves the address constant of the corresponding load module. After that, I set up protection.

[0008] Therefore, it is possible to guarantee cooperation between the protectable load module and the unprotectable load module, avoid a decrease in system processing capacity, and prevent area destruction.

[0009]

Embodiment Next, the structure and operation of an embodiment of the present invention will be explained in detail using FIGS. 2 and 3. In FIG. 2, a multi-module configuration load module 1 is a load module in which a mix of protectable load modules and unprotectable load modules is compiled and linked.
This is a main memory resident load module of ing System. This main memory resident load module is created by forming (compiling and linking) into one load module a wide variety of control load modules for efficiently performing system performance, control, and management.

The load module reorganization control data 3 is as follows:
Protect target data (for example, module name, etc.), non-protect target data for separating the protectable load module and unprotectable load module that configure the multi-module configuration load module 1,
This includes protect boundary data that determines the boundary between the two.

[0011] The load module re-editing unit 2 divides each load module of the multi-module configuration load module 1 into load modules that can be protected and load modules that cannot be protected based on the load module reorganization control data 3. Here, load modules that can be protected are grouped first (hatched rectangle in the figure), and load modules that cannot be protected are then grouped together (rectangle in the figure) to create one reedited load module 4. It is registered in the system library 41 in advance.

The re-editing load module 4 extracts the load modules that can be protected from among the load modules that make up the multi-module configuration load module 1 and puts them together (the diagonally lined rectangle in the figure), and then extracts the load modules that can be protected (the diagonally lined rectangle in the figure). Extract and summarize possible load modules (
(rectangle in the figure) is one load module. By this re-editing, the load module group that can be protected and the load module group that cannot be protected are classified into two groups.

The load module expansion unit 5 is one of the processes constituting the system initialization processing unit 51, and when the system is started, it extracts the entire load module from the re-edited load module 4 stored in advance in the system library 41. The size is determined, and the boundary is adjusted so that the boundary between the load module that can be protected and the load module that cannot be protected is in the protection application unit (for example, 4 KB or 64 KB unit) of the main memory, and an area is allocated and loaded. During this loading, address constants in each load module are re-resolved to correct addresses caused by rearrangement of load modules, and are expanded to the main memory resident area program area. After that, protection is applied to the area to be protected (see FIG. 3).

Next, the operation of deploying the configuration of FIG. 2 to the main memory will be described in detail in accordance with the order shown in the flowchart of FIG. In FIG. 3, S1 is the multiple load module 7
Find the size of the entire load module from the load module management information. S2 obtains the offset of the protected boundary module b from the multiple load module 7 (the relative address of the protected boundary load module within the multiple load module 7). This calculates the offset of the protected boundary module b in the upper right multiple load module 7.

[0015] In S3, the address of the protect boundary module b is rounded up to the protect application range to obtain the position of b' (see the figure on the right). S4 determines the deviation c of the boundary module b (see the figure on the right). S5 takes in the entire multiple load module 7 from a' on the main memory. S6
places the boundary module b and subsequent ones from the boundary position b'.

[0016] In S7, the address constants in each module (load module) are corrected by the difference c due to the rearrangement. In S8, a hardware main memory protect function is set for all blocks (all blocks in units of 4 KB and 64 KB) within the area to be protected. By the above,
At startup, load modules that can be protected from multiple load modules (re-edit load module 4 in FIG. 2) 7 are loaded into the protected area, and load modules that cannot be protected are loaded into the non-protected area after boundary adjustment. After correcting the address constant of the corresponding load module by the amount of deviation c, the main memory protect function is set for the area to be protected. As a result, the main memory protection target area can only be referenced, writing is prohibited, and the storage area is protected from destruction.

[0017]

[Effects of the Invention] As explained above, according to the present invention,
Multiple module configuration A configuration is adopted in which the protectable load modules and unprotectable load modules of load module 1 are collectively adjusted and expanded onto main memory, address constants are resolved, and protection is set. Therefore, it is possible to guarantee cooperation between the protectable load module and the unprotectable load module in the multi-module configuration load module 1, avoid a decrease in system processing capacity, and prevent area destruction. This makes effective use of the hardware protection function, helps prevent area destruction of the main storage area, and detects abnormal programs that attempt to destroy the area, thereby preventing malfunctions of system control programs due to area destruction. This greatly contributes to the high reliability of the system.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing the principle configuration of the present invention.

FIG. 2 is a configuration diagram of one embodiment of the present invention.

FIG. 3 is a flowchart explaining the operation of the present invention.

FIG. 4 is an explanatory diagram of the prior art.

[Explanation of symbols]

1: Multiple module configuration load module 2: Load module reediting unit 3: Load module reediting control data 4: Reediting load module 41: System library 5: Load module expansion unit 51: System initialization processing unit 6: Main memory program Area 7: Multiple load modules

Claims (1)

[Claims] Claim 1: A multiple load module protection method for protecting multiple load modules on main memory, comprising: a load module (1) having a multiple module configuration consisting of a protectable load module and an unprotectable load module; A load module expansion unit that adjusts the protect boundaries of the load modules that can be protected and that cannot be protected in the configuration load module (1), expands them onto the main memory, and re-resolves the address constants of each load module. (5) A multiple load module protection method, characterized in that the load module expansion unit (5) sets protection in an area of a protectable load module expanded by the load module expansion unit (5).