Multi-zone redundancy recovery method based on ECC failure scenario

Abstract

The invention discloses a multi-zone redundant recovery method based on an ECC failure scenario, and relates to the technical field of multi-zone redundant recovery. The invention comprises file burning verification, kernel file verification and early warning prompts, and analyzes the firmware burning stage, executes the corresponding firmware burning import operation, verifies whether the firmware burning is successful, and performs pre-startup verification on the imported kernel file, analyzes and obtains the verification status corresponding to the main kernel file and the file backup status corresponding to the backup kernel file, thereby performing corresponding kernel file error correction, further enhancing the startup reliability and self-repairing capability of the system, reducing the additional hardware cost of system maintenance, realizing redundant storage of data, and simultaneously, when the data cannot be corrected based on the ECC technology, the abnormal kernel file can be corrected in time based on the multi-zone redundancy, thereby reducing the risk of single point failure and improving security.

Description

Technical Field

[0001] The present invention relates to the technical field of multi-zone redundancy recovery, and in particular to a multi-zone redundancy recovery method based on an ECC failure scenario. Background Art

[0002] With the widespread application of embedded systems, users are able to experience efficient and reliable applications. However, if they are not used for a long time or in a high temperature environment, data retention errors will occur. Therefore, it is necessary to provide a redundant startup mechanism to reduce the error rate and provide redundant guarantees for reliability from the data source. Even if the system detects defects using ECC technology, ECC cannot correct the errors. Multi-zone redundancy can repair data in storage partitions with too many bit flips, thereby further improving the redundancy and recovery of system startup.

[0003] Prior art, such as a storage device disclosed in an invention patent application with publication number CN113342577B, comprises: at least one storage array; the storage array comprises a plurality of storage chips; each of the plurality of storage chips comprises a plurality of storage planes; each of the plurality of storage planes comprises a plurality of storage pages numbered according to the same numbering rule; the storage array comprises a first storage area; the first storage area comprises at least one storage page row; the storage page row comprises a plurality of storage pages with the same number in the plurality of storage planes; each storage page in the first storage area is used to store first verification data; wherein the first verification data comprises verification data of storage data of the remaining storage pages in the storage plane to which the corresponding storage page belongs.

[0004] In view of the above scheme, the applicant of the present invention has found that the above technical problems have at least the following technical problems: the above invention mainly recovers data from multiple erroneous data, and does not screen out the burning tool required for the corresponding burning of the firmware, and thus cannot complete the corresponding burning of the firmware, cannot be analyzed from the import perspective of the firmware burning, cannot know the current status of the firmware after burning, whether the burning is successful and successfully stored in the Flash, and cannot perform ECC verification on the stored kernel file before startup. It is impossible to know whether the main kernel file and backup kernel file currently stored in different Flash are in a state that can normally start the system, and cannot perform corresponding data error correction on the kernel data with abnormal verification status, which will greatly reduce the security of the system data and cannot ensure the integrity of the system data. Summary of the invention

[0005] In view of the above-mentioned technical deficiencies, the purpose of the present invention is to provide a multi-zone redundancy recovery method based on ECC failure scenarios.

[0006] To solve the above technical problems, the present invention adopts the following technical solutions: The present invention provides a multi-zone redundant recovery method based on an ECC failure scenario, including: Step 1, file burning verification: First, select the corresponding burning tool when the firmware enters the burning stage, and then execute the corresponding firmware burning import operation, and verify whether the firmware burning is successful.

[0007] Step 2, kernel file verification: After the firmware is successfully burned, start the system and perform a pre-startup check on the imported kernel file to analyze the verification status of the main kernel file. If the verification status of the main kernel file is abnormal, perform the corresponding mirror check on the backup kernel file to obtain the file backup status of the backup kernel file, and analyze the corresponding error correction method after the main kernel file verification fails and the corresponding measures to be taken when all kernel files fail to verify.

[0008] Step 3: Warning prompt: When both kernel image verifications fail, a warning prompt will be issued.

[0009] Compared with the prior art, the beneficial effects of the present invention are: 1. The present invention provides a multi-zone redundant recovery method based on an ECC failure scenario, by analyzing the firmware burning stage, executing the corresponding firmware burning import operation, and verifying whether the firmware burning is successful, and at the same time performing a pre-startup check on the imported kernel file, analyzing to obtain the check status corresponding to the main kernel file and the file backup status corresponding to the backup kernel file, thereby performing corresponding kernel file error correction, further enhancing the system's startup reliability and self-repair capability, reducing the additional hardware cost of system maintenance, realizing redundant storage of data, and solving the deficiencies in the current technology. At the same time, based on the use of ECC technology to verify the kernel file, efficient kernel file verification is realized, and the verification efficiency is improved. To a certain extent, the abnormal kernel file can be corrected in time based on multi-zone redundant support, and important data protection measures are provided for application requirements for frequent startup, reducing the risk of single point failures, improving the stability and reliability of the system, and providing higher security.

[0010] 2. According to the corresponding burning tools when the firmware enters the burning stage, the corresponding firmware burning import operation is performed to verify whether the firmware burning is successful, thereby fully protecting the data integrity of the firmware when it enters the burning stage, providing strong judgment support for subsequent verification, reducing query time, and improving data availability.

[0011] 3. Based on the pre-startup verification of the imported kernel file, the verification status corresponding to the main kernel file and the file backup status corresponding to the backup kernel file are understood, and the corresponding error correction method after the main kernel file verification fails and the corresponding measures to be taken when all kernel files fail to verify are analyzed, so as to achieve comprehensive ECC kernel file verification, provide redundant error correction support for abnormal kernel files in a timely manner, ensure data integrity, reduce the risk of single point failures, and avoid data inconsistency problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0013] Figure 1 The present invention is a schematic flow chart of the steps for implementing the method. DETAILED DESCRIPTION

[0014] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0015] See also Figure 1 As shown, the multi-zone redundant recovery method based on the ECC failure scenario includes: Step 1, file burning verification: first, filter out the corresponding burning tool when the firmware enters the burning stage, then execute the corresponding firmware burning import operation, and verify whether the firmware burning is successful.

[0016] It should be noted that the type and Flash type corresponding to the current device are obtained from the settings. Flash refers to the Flash memory. The various burning tools include JTAG, UART, USB, SWD, OpenOCD and U-Boot.

[0017] As an optional implementation, the filtering out of the burning tool corresponding to the firmware when entering the burning stage, the specific filtering process is as follows: obtain the type and Flash type corresponding to the current device, and compare the type corresponding to the current device with the device type corresponding to each burning tool and also compare the type corresponding to the Flash with the Flash type corresponding to each burning tool. If the type corresponding to the current device is the same as the device type corresponding to a certain burning tool and the type corresponding to the Flash is the same as the Flash type corresponding to the burning tool, then the burning tool is used as the burning tool corresponding to the firmware when entering the burning stage, so as to filter out the burning tool corresponding to the firmware when entering the burning stage.

[0018] As an optional implementation, the corresponding firmware burning and importing operation is executed, and the specific execution process is as follows: first, compile and package the firmware, specify the processor architecture and compilation options corresponding to the target device, and then use the compiler to compile the source code file selected corresponding to the specified target device into a target file, and then generate the corresponding executable file based on the linker, and then integrate the executable file into an integrated firmware file based on the packaging tool and other resource files, and burn it based on the screened burning tool. Before burning, it is necessary to ensure that the target device and the host are normally connected. Select the solid file to be burned in the burning tool, and configure the corresponding parameters. The parameters are the burning address range. When the configuration is completed, start the burning tool to generate the corresponding burning file, including the kernel file and the bootloader file, and the tool will automatically write the solid file to the corresponding designated location of the Flash memory, where the designated location is the kernel file saved in NANDFlash in a double redundant form, and the bootloader file is saved in NorFlash, thereby completing the corresponding firmware burning and importing operation.

[0019] It should be noted that the source code files include C language code, C++, Java, Python and HTML, etc., the target file is o file, and other resource files include configuration files and data files, etc. The packaging tools include binwalk and mkimage. Binwalk can decompress the firmware file to obtain its various components; mkimage is used to repackage the modified file into the firmware format. The packaging format can be binary format, HEX format or other specific format, depending on the burning method of the target device and the supported file format.

[0020] As an optional implementation, the verification of whether the firmware burning is successful, the specific verification process is as follows: by reading the burning file stored in each Flash, and comparing the burning file imported into each Flash with the original firmware file, if the burning file imported into a certain Flash is inconsistent with the original firmware file, it is determined that the firmware burning has failed, and the corresponding burning operation is re-executed; conversely, if the burning file imported into a certain Flash is consistent with the original firmware file, it is determined that the firmware burning is successful, thereby verifying whether the firmware burning is successful.

[0021] By screening out the corresponding burning tools when the firmware enters the burning stage, and executing the corresponding firmware burning import operation, it is verified whether the firmware burning is successful, thereby achieving comprehensive protection of the data integrity of the firmware when entering the burning stage, providing strong judgment support for subsequent verification, reducing query time, and improving data availability.

[0022] Step 2, kernel file verification: After the firmware is successfully burned, start the system and perform a pre-startup check on the imported kernel file to analyze the verification status of the main kernel file. If the verification status of the main kernel file is abnormal, perform the corresponding mirror check on the backup kernel file to obtain the file backup status of the backup kernel file, and analyze the corresponding error correction method after the main kernel file verification fails and the corresponding measures to be taken when all kernel files fail to verify.

[0023] It should be noted that Ecc includes parity check, hash function and CRC, among which CRC is cyclic redundancy check.

[0024] It should be noted that the corresponding Ecc algorithm is selected based on the verification requirements corresponding to the current main kernel file. For example, if the main kernel file is currently mainly verified to have abnormal errors, CRC can be selected.

[0025] As an optional implementation, the analysis obtains the verification status corresponding to the main kernel file, and the specific analysis process is as follows: T1. By selecting the corresponding Ecc algorithm, and then using the Ecc algorithm to generate the corresponding Ecc code from the main kernel file, and extracting the main information corresponding to the main kernel file from the generated Ecc code, wherein the main information includes floating-point values, redundant bits and field lengths, and performing standardization processing on the main information corresponding to the main kernel file.

[0026] T2. Input the main information corresponding to the processed main kernel file into the Ecc algorithm model, and then output the image verification result corresponding to the main kernel file. If the image verification result output value corresponding to the main kernel file is 1, it is determined that the image verification corresponding to the main kernel file is successful, and the system program is started directly. If the image verification result output value corresponding to the main kernel data is 0, it is determined that the image verification corresponding to the main kernel file has failed, and the file backup status corresponding to the main kernel file is determined to be abnormal, so as to analyze and obtain the verification status corresponding to the main kernel file.

[0027] As an optional implementation, the analysis obtains the image verification result corresponding to the main kernel file, and the specific analysis process is as follows: by calculating the formula: The analysis results are as follows: η, β, and φ are the image verification results corresponding to the main kernel file, η, β, and φ are the floating point values ​​corresponding to the main kernel file, and φ is the redundant bit corresponding to the main kernel file. is the field length corresponding to the main kernel file, δ is the set reference main kernel data value, m1, m2 and m3 are the set floating point value weight factor, redundant bit weight factor and field length weight factor respectively, 0<m1<1, 0<m2<1, 0<m3<1.

[0028] It should be noted that the initial main kernel data value generated by the main kernel file based on Ecc is used as the reference main kernel data value.

[0029] It should be noted that the weight factor of the floating-point value, the weight factor of the redundant bit and the weight factor of the field length are obtained through factor analysis. The information of the floating-point value, the redundant bit and the field length is condensed first, and then the corresponding variance explanation rate is obtained, and then divided by the variance explanation rate to get the corresponding weight.

[0030] It should also be noted that information condensation refers to condensing multiple analysis items into several key summary indicators, and the variance explanation rate refers to the contribution of each principal component or factor to the overall variance, usually expressed as a percentage, indicating how much information the factor contains about the original data.

[0031] As an optional implementation, the verification obtains the file backup status corresponding to the backup kernel file, and the specific verification process is as follows: F1. Based on the selected Ecc algorithm, the Ecc algorithm is used to generate the corresponding Ecc value for the backup kernel file, and the Ecc value generated by the backup kernel file is used as backup information, wherein the backup information includes bit values, hash values ​​and byte values, and the backup information corresponding to the backup kernel file is normalized.

[0032] F2. Input the processed backup kernel information into the Ecc algorithm model, and then output the image verification result corresponding to the backup kernel data. If the image verification result output value corresponding to the backup kernel data is 1, it is determined that the image verification corresponding to the backup kernel file is successful, and the backup kernel image address of the successful verification is obtained, and the kernel is set as the main application for this boot. If the image verification result output value corresponding to the backup kernel data is 0, it is determined that the image verification corresponding to the backup kernel file fails, and the file backup status corresponding to the backup kernel file is abnormal, so as to verify and obtain the file backup status corresponding to the backup kernel file.

[0033] As an optional implementation, the analysis obtains the mirror verification result corresponding to the backup kernel data, and the specific analysis process is as follows: by calculating the formula: Analyze and obtain the image verification results corresponding to the backup kernel data A is the bit corresponding to the backup kernel, B is the hash value corresponding to the backup kernel, C is the byte value corresponding to the backup kernel, Q is the set reference backup data value, n1, n2 and n3 are the set bit weight factor, hash value weight factor and byte value weight factor respectively, 0<n1<1, 0<n2<1, 0<n3<1.

[0034] It should also be noted that the initial backup data value generated by the backup kernel file based on Ecc is used as the reference backup data value.

[0035] It should also be noted that the corresponding Ecc algorithm is selected based on the verification requirements corresponding to the current backup kernel file. For example, if the backup kernel file is currently mainly verified to have abnormal errors, a cyclic redundancy check or a hash function can be selected.

[0036] It should be noted again that the weight factor of the bit, the weight factor of the hash value and the weight factor of the byte value are obtained through factor analysis. The information of the bit value, hash value and byte value is first condensed, and then the corresponding variance explanation rate is obtained, and then divided by the variance explanation rate to get the corresponding weight.

[0037] As an optional implementation, the specific analysis process of analyzing the error correction method corresponding to the failure of the main kernel file verification is as follows: when the main kernel file verification status is abnormal and Ecc cannot complete the correction of the main kernel file data abnormality, and the backup kernel file image verification is successful, and the backup file data status presented is normal, then the main kernel image address that failed the verification is obtained, and the normal backup kernel content is rewritten to the main kernel area of ​​NANDFlash, which is used for the main kernel to repair the data bits, so as to analyze the error correction method corresponding to the failure of the main kernel file verification.

[0038] As an optional implementation method, the corresponding measures to be taken when all kernel files fail to be verified are analyzed. The specific analysis process is as follows: the verification error display abnormal data corresponding to the current kernel files are compared with the kernel files corresponding to the historical abnormal phenomenon data stored in the database. If the verification error display abnormal data corresponding to a current kernel file is the same as the kernel file corresponding to the historical abnormal phenomenon data stored in the database, then the measures taken after the verification abnormality of the historical kernel file are used as the measures taken corresponding to the current kernel file, and so on, the corresponding measures to be taken when all kernel files fail to be verified are analyzed.

[0039] It should be noted that taking measures includes selecting to start the safe mode or permanently keeping the error log to perform user intervention.

[0040] Based on the pre-startup verification of the imported kernel file, the verification status corresponding to the main kernel file and the file backup status corresponding to the backup kernel file are understood, and the corresponding error correction method after the main kernel file verification fails and the corresponding measures to be taken when the verification of each kernel file fails are analyzed. In this way, comprehensive ECC kernel file verification is achieved, and redundant error correction support is provided for abnormal kernel files in a timely manner, thereby ensuring data integrity, reducing the risk of single point failures, and avoiding data inconsistency problems.

[0041] Step 3: Warning prompt: When both kernel image verifications fail, a warning prompt will be issued.

[0042] The embodiment of the present invention provides a multi-zone redundant recovery method based on an ECC failure scenario, by analyzing the firmware burning stage, executing the corresponding firmware burning import operation, and verifying whether the firmware burning is successful, and at the same time performing a pre-startup check on the imported kernel file, analyzing to obtain the check status corresponding to the main kernel file and the file backup status corresponding to the backup kernel file, thereby performing corresponding kernel file error correction, further enhancing the system's startup reliability and self-repair capability, reducing the additional hardware cost of system maintenance, realizing redundant storage of data, and solving the deficiencies in the current technology. At the same time, based on the use of ECC technology to verify the kernel file, efficient kernel file verification is realized, and the verification efficiency is improved. To a certain extent, the abnormal kernel file can be timely corrected based on multi-zone redundant support errors, and important data protection measures are provided for application requirements for frequent startup, reducing the risk of single point failures, improving the stability and reliability of the system, and providing higher security.

[0043] The above contents are merely examples and explanations of the concept of the present invention. Those skilled in the art may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the concept of the invention or exceed the scope defined in this specification, they shall all fall within the protection scope of the present invention.

Claims

1. A multi-zone redundancy recovery method based on ECC failure scenario, characterized in that: include: Step 1: File burning verification: First, select the corresponding burning tool when the firmware enters the burning stage, then perform the corresponding firmware burning import operation, and verify whether the firmware burning is successful; Step 2, kernel file verification: after the firmware is successfully burned, the system is started and the imported kernel file is verified before startup, and the verification status corresponding to the main kernel file is analyzed. If the verification status corresponding to the main kernel file is abnormal, the corresponding mirror verification is performed on the backup kernel file to verify the file backup status corresponding to the backup kernel file, and the corresponding error correction method after the main kernel file verification fails and the corresponding measures to be taken when all kernel files fail to verify are analyzed; Step 3: Warning prompt: When both kernel image verifications fail, a warning prompt will be issued.

2. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The specific screening process of selecting the corresponding burning tool when the firmware enters the burning stage is as follows: Get the type and Flash type corresponding to the current device, and compare the type corresponding to the current device with the device type supported by each burning tool. Also compare the type corresponding to Flash with the Flash type supported by each burning tool. If the type corresponding to the current device is the same as the device type supported by a burning tool, and the type corresponding to Flash is the same as the Flash type supported by the burning tool, then use the burning tool as the burning tool corresponding to the firmware when it enters the burning stage, so as to filter out the burning tool corresponding to the firmware when it enters the burning stage.

3. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The specific execution process of the corresponding firmware burning and importing operation is as follows: First, compile and package the firmware. By specifying the processor architecture and compilation options corresponding to the target device, use the compiler to compile the selected source code file corresponding to the specified target device into a target file, and then generate the corresponding executable file based on the linker. Secondly, integrate the executable file into a firmware file based on the packaging tool and other resource files, and burn it based on the selected burning tool. Before burning, it is necessary to ensure that the target device and the host are connected normally. Select the solid file to be burned in the burning tool and configure the corresponding parameters. The parameters are the burning address range. When the configuration is completed, start the burning tool to generate the corresponding burning file, including the kernel file and the bootloader file, and the tool will automatically write the solid file to the corresponding specified location of the Flash memory. The specified location is the kernel file saved in NANDFlash in a double redundant form, and the bootloader file is saved in NorFlash, so as to complete the corresponding firmware burning and import operation.

4. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 3, characterized in that: The verification process of whether the firmware is successfully burned is as follows: By reading the burning files stored in each Flash and comparing the burning files imported into each Flash with the original firmware files, if the burning file imported into a Flash is inconsistent with the original firmware file, it is determined that the firmware burning has failed, and the corresponding burning operation is re-executed. On the contrary, if the burning file imported into a Flash is consistent with the original firmware file, it is determined that the firmware burning is successful, so as to verify whether the firmware burning is successful.

5. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The analysis obtains the verification status corresponding to the main kernel file, and the specific analysis process is as follows: T1, by selecting a corresponding Ecc algorithm, and then using the Ecc algorithm to generate a corresponding Ecc code from the main kernel file, and extracting the main information corresponding to the main kernel file from the generated Ecc code, wherein the main information includes a floating point value, redundant bits and field length, and performing standardization processing on the main information corresponding to the main kernel file; T2. Input the main information corresponding to the processed main kernel file into the Ecc algorithm model, and then output the image verification result corresponding to the main kernel file. If the image verification result output value corresponding to the main kernel file is 1, it is determined that the image verification corresponding to the main kernel file is successful, and the system program is started directly. If the image verification result output value corresponding to the main kernel data is 0, it is determined that the image verification corresponding to the main kernel file has failed, and the file backup status corresponding to the main kernel file is determined to be abnormal, so as to analyze and obtain the verification status corresponding to the main kernel file.

6. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 5, characterized in that: The analysis obtains the image verification result corresponding to the main kernel file. The specific analysis process is as follows: By calculation formula: The analysis results are as follows: η, β, and φ are the image verification results corresponding to the main kernel file, η, β, and φ are the floating point values ​​corresponding to the main kernel file, and φ is the redundant bit corresponding to the main kernel file. is the field length corresponding to the main kernel file, δ is the set reference main kernel data value, m1, m2 and m3 are the set floating point value weight factor, redundant bit weight factor and field length weight factor respectively, 0<m1<1, 0<m2<1, 0<m3<1.

7. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The verification obtains the file backup status corresponding to the backup kernel file, and the specific verification process is as follows: F1. Based on the selected Ecc algorithm, the Ecc algorithm is used to generate a corresponding Ecc value for the backup kernel file, and the Ecc value generated by the backup kernel file is used as backup information, wherein the backup information includes a bit value, a hash value, and a byte value, and the backup information corresponding to the backup kernel file is normalized; F2. Input the processed backup kernel information into the Ecc algorithm model, and then output the image verification result corresponding to the backup kernel data. If the image verification result output value corresponding to the backup kernel data is 1, it is determined that the image verification corresponding to the backup kernel file is successful, and the backup kernel image address of the successful verification is obtained, and the kernel is set as the main application for this boot. If the image verification result output value corresponding to the backup kernel data is 0, it is determined that the image verification corresponding to the backup kernel file fails, and the file backup status corresponding to the backup kernel file is abnormal, so as to verify and obtain the file backup status corresponding to the backup kernel file.

8. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 7, characterized in that: The analysis obtains the image verification result corresponding to the backup kernel data. The specific analysis process is as follows: By calculation formula: Analyze and obtain the image verification results corresponding to the backup kernel data A is the bit corresponding to the backup kernel, B is the hash value corresponding to the backup kernel, C is the byte value corresponding to the backup kernel, Q is the set reference backup data value, n1, n2 and n3 are the set bit weight factor, hash value weight factor and byte value weight factor respectively, 0<n1<1, 0<n2<1, 0<n3<1.

9. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The specific analysis process of analyzing the corresponding error correction method after the main kernel file verification fails is as follows: When the main kernel file verification status is abnormal and Ecc cannot complete the correction of the main kernel file data abnormality, but the backup kernel file image verification is successful and the backup file data status presented is normal, the main kernel image address that failed the verification is obtained, and the normal backup kernel content is rewritten to the main kernel area of ​​NANDFlash for the main kernel to repair the data bits, so as to analyze the corresponding error correction method after the main kernel file verification fails.

10. The multi-zone redundancy recovery method based on ECC failure scenario according to claim 1, characterized in that: The corresponding measures to be taken when the analysis shows that all kernel files fail to be verified are as follows: Compare the verification error display abnormal data corresponding to each current kernel file with the kernel files corresponding to each historical abnormal phenomenon data stored in the database. If the verification error display abnormal data corresponding to a current kernel file is the same as the kernel file corresponding to a historical abnormal phenomenon data stored in the database, then the measures taken after the verification abnormality of the historical kernel file will be used as the measures taken corresponding to the current kernel file, and so on. The corresponding measures taken when the verification of each kernel file fails are analyzed.

Images