Kernel test task management method and device, electronic equipment and storage medium

By automating the kernel test task management method, the problem of inefficient creation and termination of tasks in existing tools is solved, efficient kernel vulnerability mining is achieved, and large-scale vulnerability detection is supported.

CN120104486APending Publication Date: 2025-06-06TSINGHUA UNIVERSITY +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510173955.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-02-17
Publication Date
2025-06-06

AI Technical Summary

Technical Problem

The existing Linux kernel vulnerability mining tool syzkaller requires users to manually create and terminate test tasks, which leads to low efficiency in kernel vulnerability mining and difficult to support large-scale vulnerability mining.

Method used

Provides a kernel test task management method, automatically determines test resources through configuration information sent by user terminals, creates and manages the process of kernel test tasks, including automatically creating and ending task processes, ensuring the automated process of tasks and efficient utilization of the computing resources of the test node server.

Benefits of technology

It improves the efficiency of kernel vulnerability mining, reduces manual intervention, shortens kernel test preparation time, ensures the automated process of kernel test tasks and efficient utilization of computing resources, and supports large-scale kernel vulnerability mining.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120104486A_ABST
    Figure CN120104486A_ABST
Patent Text Reader

Abstract

The invention discloses a kernel test task management method and device, electronic equipment and a computer storage medium, and is applied to a management node server, the method comprises the following steps: determining test resources of a kernel test task according to configuration information sent by a user terminal; based on the test resources, creating a first task process for managing a kernel test task; sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing a kernel test task based on the test instance creation command; and when it is detected through the polling thread that the kernel test task meets a preset ending condition, ending the first task process and the second task process. In the whole process, the kernel test task is automatically created and terminated, and computing resources of the test node server are fully utilized, so that the kernel vulnerability mining efficiency can be effectively improved, and large-scale kernel vulnerability mining is facilitated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of kernel vulnerability mining, and in particular to a kernel test task management method, device, electronic device and storage medium. Background Art

[0002] The Linux kernel is mainly written in C language, which lacks a built-in memory security management mechanism. Therefore, it is prone to kernel vulnerabilities such as UAF (Use-After-Free) and OOB (Out-Of-Bounds). These vulnerabilities may lead to serious consequences such as privilege escalation, system crash or remote code execution.

[0003] At present, the mainstream Linux kernel vulnerability mining tool is syzkaller, which discovers security vulnerabilities in the kernel through system call fuzzing. However, when using syzkaller, users often need to manually create test tasks and manually terminate the tasks after the test, which is not conducive to large-scale kernel vulnerability mining and has the problem of low kernel vulnerability mining efficiency. Summary of the invention

[0004] The embodiments of the present application provide a kernel test task management method, device, electronic device and computer storage medium, which can improve the efficiency of kernel vulnerability mining and facilitate large-scale kernel vulnerability mining.

[0005] In a first aspect, an embodiment of the present application provides a kernel test task management method, which is applied to a management node server, and the method includes:

[0006] Determine the test resources for the kernel test task according to the configuration information sent by the user terminal;

[0007] Based on the test resources, create a first task process for managing the kernel test task;

[0008] Sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command;

[0009] When it is detected through the polling thread that the kernel test task meets the preset termination condition, the first task process and the second task process are terminated.

[0010] In a possible implementation, the configuration information includes a test kernel type, a test kernel version number, and a test case template library;

[0011] According to the configuration information sent by the user terminal, the test resources of the kernel test task are determined, including:

[0012] Determine the test target kernel object and the test target disk image of the kernel test task according to the test kernel type and the test kernel version number;

[0013] Determine the test case template set for the kernel test task according to the test case template library;

[0014] Determine the fuzz testing engine for the kernel testing task based on the test kernel type, test kernel version number and test case template library.

[0015] In a possible implementation, the configuration information includes storage path information of the test resources, address information of each test node server, and virtual machine resource configuration information on each test node server;

[0016] Before creating a first task process for managing the kernel test task based on the test resources, the method further includes:

[0017] Generate a configuration file of the fuzzy test engine based on the storage path information of the test resources, the address information of each test node server and the virtual machine resource configuration information on each test node server;

[0018] Based on the test resources, a first task process for managing the kernel test task is created, including:

[0019] The test resources are called through the configuration file of the fuzz test engine to create a first task process for managing the kernel test task.

[0020] In a possible implementation, before sending a test instance creation command to at least one test node server through the first task process so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command, the method further includes:

[0021] The test target kernel object and the test target disk image are sent to each test node server; the test target kernel object and the test target disk image are used to create a second task process in each test node server.

[0022] In a possible implementation, the configuration information includes a test target duration and a test target crash count;

[0023] When it is detected through the polling thread that the kernel test task meets the preset termination condition, the first task process and the second task process are terminated, including:

[0024] When it is detected through the polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number, the first task process and the second task process are terminated.

[0025] In a possible implementation, the method further includes:

[0026] Receiving a task stop command sent by a user terminal for a kernel test task;

[0027] In response to the task stop command, pausing the first task process and the second task process;

[0028] Receiving a task recovery command sent by a user terminal for a kernel test task;

[0029] In response to the task resumption command, the first task process and the second task process are resumed.

[0030] In a possible implementation, when it is detected through the polling thread that the kernel test task satisfies a preset termination condition, before terminating the first task process and the second task process, the method further includes:

[0031] Receive task running data sent by each test node server at a preset time interval;

[0032] Synchronize task running data to the database.

[0033] In a possible implementation, the method further includes:

[0034] Receiving a task information acquisition command sent by a user terminal for a kernel test task;

[0035] In response to the task information acquisition command, task information of the kernel test task is acquired based on the database; the task information includes at least one of the running status information of the kernel test task, the kernel version information of the kernel test task, the task completion status information of the kernel test task, and the vulnerability mining status information of the kernel test task.

[0036] In a possible implementation, when it is detected through the polling thread that the kernel test task meets the preset termination condition, after the first task process and the second task process are terminated, the method further includes:

[0037] Store the kernel test data of the kernel test task into a preset storage path;

[0038] The kernel test corpus of the kernel test task is stored in the database.

[0039] In a second aspect, an embodiment of the present application provides a kernel test task management device, which is applied to a management node server, and the device includes:

[0040] A resource determination module, used to determine the test resources of the kernel test task according to the configuration information sent by the user terminal;

[0041] A first creation module, used for creating a first task process for managing kernel test tasks based on test resources;

[0042] A second creation module is used to send a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command;

[0043] The task ending module is used to end the first task process and the second task process when it is detected through the polling thread that the kernel test task meets the preset ending condition.

[0044] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps provided in the first aspect of the embodiment of the present application.

[0045] In a fourth aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method steps provided in the first aspect of the embodiment of the present application.

[0046] The kernel test task management method, device, electronic device and computer storage medium are applied to the management node server, and the test resources of the kernel test task are determined according to the configuration information sent by the user terminal, and the test environment is configured based on the test resources, and the first task process for managing the kernel test task is automatically created, which reduces manual intervention and shortens the kernel test preparation time; through the first task process, a test instance creation command is sent to at least one test node server, so that each test node server automatically creates a second task process for executing the kernel test task based on the test instance creation command, which can not only ensure the automation process of the kernel test task, but also make full use of the computing resources of the test node server, effectively improve the computing power of the kernel test, and speed up the kernel test; when the kernel test task meets the preset termination condition through the polling thread, the first task process and the second task process are automatically terminated, which improves the automation level of the kernel test task management, and the kernel test task can be terminated in time without manual monitoring. The entire kernel test task management process can effectively improve the efficiency of kernel vulnerability mining by automatically creating and terminating the kernel test task and making full use of the computing resources of the test node server, which is conducive to large-scale kernel vulnerability mining. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0048] Figure 1 A schematic diagram of an application environment of a kernel test task management method provided by an exemplary embodiment of the present application;

[0049] Figure 2 A flowchart of a kernel test task management method provided by an exemplary embodiment of the present application;

[0050] Figure 3 A flowchart of another kernel test task management method provided by an exemplary embodiment of the present application;

[0051] Figure 4 A schematic diagram of the architecture of a kernel test task management method provided by an exemplary embodiment of the present application;

[0052] Figure 5 A schematic diagram of the structure of a kernel test task management device is provided for an exemplary embodiment of the present application;

[0053] Figure 6 A structural schematic diagram of an electronic device is provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0055] In the description of the present application, it should be understood that the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0056] The kernel test task management method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the user terminal 10 communicates with the management node server 20 through the network, and the management node server 20 communicates with at least one test node server (test node server 31, test node server 32, test node server 33...) through the network. The data storage system 40 can store the data that the management node server 20 needs to process. The data storage system 40 can be integrated on the management node server 20, or it can be placed on the cloud or other network servers. The management node server 20 determines the test resources of the kernel test task according to the configuration information sent by the user terminal 10; based on the test resources, creates a first task process for managing the kernel test task; through the first task process, sends a test instance creation command to at least one test node server, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command; when the kernel test task is detected to meet the preset end condition through the polling thread, the first task process and the second task process are terminated.

[0057] It is worth noting that the user terminal 10 can be implemented as an independent terminal or a terminal cluster composed of multiple terminals. The user terminal 10 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The management node server 20 can be implemented as an independent server or a server cluster composed of multiple servers.

[0058] In one embodiment, Figure 2 As shown, a kernel test task management method is provided, which is applied to Figure 1 Taking the management node server 20 in the example as an example, the following steps are included:

[0059] S201: Determine test resources for a kernel test task according to configuration information sent by a user terminal.

[0060] Optionally, the user fills in the task name, test target duration, test target crash number, test kernel type, test kernel version number, test case template library and other configuration information of the kernel test task in the Web UI interface of the user terminal. The user terminal sends the configuration information filled in by the user to the management node server. The task management module running on the management node server receives the configuration information sent by the user terminal, and automatically determines the test resources for configuring the test environment of the kernel test task according to the configuration information, including the test target disk image, the test case template set, the fuzzy test engine for executing the kernel test task, etc.

[0061] In this embodiment, the management node server automatically determines the test resources according to the configuration information filled in by the user, which reduces manual intervention, shortens the preparation time of the kernel test task, and effectively improves the efficiency of kernel vulnerability mining.

[0062] S202: Based on the test resources, create a first task process for managing kernel test tasks.

[0063] Optionally, the task management module running on the management node server copies the test resources to a preset storage path (such as a preset task-specific directory) on the management node server, and sends the test target kernel object and the test target disk image in the test resources to each test node server. Then the task management module automatically generates a configuration file of a fuzzy test engine for executing the kernel test task, and calls the test resources through the configuration file of the fuzzy test engine, and creates a first task process for managing the kernel test task on the management node server.

[0064] In this embodiment, the task management module running on the management node server automatically creates a first task process for managing kernel test tasks based on test resources, which can ensure the automation process of kernel test tasks and effectively improve the efficiency of kernel vulnerability mining.

[0065] S203: Sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command.

[0066] Optionally, after creating a first task process for managing kernel test tasks, the task management module running on the management node server starts the fuzzy test engine through the first task process, so that the fuzzy test engine connects to each test node server according to the address information of each test node server in the configuration file and the virtual machine resource configuration information on each test node server, and sends a test instance creation command to each test node server, so that each test node server runs a virtual machine based on the test instance creation command to create a second task process for executing the kernel test task. It is worth noting that the second task process data (i.e., the task running data of each test node server) will be sent to the management node server at a preset time interval, so that the management node server centrally manages and stores the data uploaded by each test node server.

[0067] In this embodiment, the task management module running on the management node server starts the fuzz test engine through the first task process, so that the fuzz test engine is connected to each test node server according to the configuration file, and sends a test instance creation command to each test node server, so that each test node server responds to the test instance creation command and runs a virtual machine to create a second task process for executing the kernel test task. The whole process can not only ensure the automation process of the kernel test task, but also make full use of the computing resources of the test node server, effectively improve the computing power of the kernel test, speed up the kernel test, and thus improve the efficiency of kernel vulnerability mining.

[0068] S204: When it is detected through the polling thread that the kernel test task meets a preset termination condition, the first task process and the second task process are terminated.

[0069] Optionally, the task management module running on the management node server terminates the first task process and the second task process when it detects through a polling thread that the test duration of the kernel test task reaches the test target duration set by the user, or the number of test crashes of the kernel test task reaches the test target crash number set by the user.

[0070] It is worth noting that multiple task processes for managing different kernel test tasks can be run on the management node server at the same time. The task management module can detect whether all currently running kernel test tasks meet the preset end conditions by creating a polling thread, and automatically end the kernel test tasks that meet the preset end conditions, that is, end the task processes corresponding to the kernel test tasks on the management node server and each test node server.

[0071] In this embodiment, the task management module running on the management node server automatically ends the first task process and the second task process when it detects through the polling thread that the kernel test task meets the preset termination conditions, thereby improving the automation level of kernel test task management and terminating the kernel test task in a timely manner without human monitoring.

[0072] The above kernel test task management method is applied to the management node server, and the test resources of the kernel test task are determined according to the configuration information sent by the user terminal, and the test environment is configured based on the test resources, and the first task process for managing the kernel test task is automatically created, which reduces manual intervention and shortens the kernel test preparation time; through the first task process, a test instance creation command is sent to at least one test node server, so that each test node server automatically creates a second task process for executing the kernel test task based on the test instance creation command, which can not only ensure the automation process of the kernel test task, but also make full use of the computing resources of the test node server, effectively improve the computing power of the kernel test, and speed up the kernel test; when the kernel test task meets the preset termination condition through the polling thread, the first task process and the second task process are automatically terminated, which improves the automation level of the kernel test task management, and the kernel test task can be terminated in time without manual monitoring. The entire kernel test task management process can effectively improve the efficiency of kernel vulnerability mining by automatically creating and terminating the kernel test task and making full use of the computing resources of the test node server, which is conducive to large-scale kernel vulnerability mining.

[0073] In one embodiment, Figure 3 As shown, another kernel test task management method is provided, which is applied to Figure 1 Taking the management node server 20 in the example as an example, the following steps are included:

[0074] S301: Receive configuration information sent by a user terminal.

[0075] Among them, the configuration information includes the test kernel type, the test kernel version number, the test case template library, the storage path information of the test resources, the address information of each test node server, the virtual machine resource configuration information on each test node server, the test target duration and the number of test target crashes.

[0076] Optionally, the user pre-fills in the task name of the kernel test task, the test kernel type, the test kernel version number, the test case template library, the storage path information of the test resources, the address information of each test node server, the virtual machine resource configuration information on each test node server, the test target duration and the test target crash number and other configuration information in the Web UI interface of the user terminal. Then the user terminal sends the configuration information filled in by the user to the management node server, so that the management node server receives the configuration information for the kernel test task filled in by the user.

[0077] S302: Determine the test target kernel object and the test target disk image of the kernel test task according to the test kernel type and the test kernel version number.

[0078] Optionally, the task management module running on the management node server automatically selects the test target kernel object of the kernel test task from the preset kernel image library according to the test kernel type and the test kernel version number in the configuration information, and automatically selects the test target disk image of the kernel test task from the preset disk image library according to the test kernel type and the test kernel version number. It is worth noting that the user can also directly upload a customized test target kernel object or a test target disk image, and the specific sources of the test target kernel object and the test target disk image are not limited in the embodiments of the present application.

[0079] S303: Determine a test case template set for the kernel test task according to the test case template library.

[0080] The test case template library includes a plurality of preset test case templates, each of which is used to guide the generation and mutation of test cases in the kernel test task.

[0081] Optionally, the task management module running on the management node server automatically selects at least one test case template from the test case template library to form a test case template set for the kernel test task based on the configuration information pre-filled by the user, thereby guiding the generation and mutation of the test cases for the kernel test task. It is worth noting that the user can also directly specify at least one test case template in the test case template library to form a test case template set, or upload a customized test case template to form a test case template set. The specific source of the test case template set is not limited in the embodiments of the present application.

[0082] S304: Determine the fuzzy test engine for the kernel test task according to the test kernel type, the test kernel version number and the test case template library.

[0083] Optionally, the task management module running on the management node server automatically searches for a matching fuzzy test engine from the fuzzy test engine library as the fuzzy test engine for the kernel test task based on the test kernel type, test kernel version number and test case template library, such as using syzkaller as the fuzzy test engine for the kernel test task.

[0084] In this embodiment, the task management module on the management node server automatically determines the test target kernel object, test target disk image and test case template library of the kernel test task according to the user's configuration information for the kernel test task, thereby reducing the time required for human intervention and effectively improving the efficiency of kernel vulnerability mining.

[0085] S305: Generate a configuration file of the fuzzy test engine based on the storage path information of the test resources, the address information of each test node server, and the virtual machine resource configuration information on each test node server.

[0086] Among them, the storage path information of the test resources includes but is not limited to the root directory address for storing test resources on the test node server; the address information of each test node server includes but is not limited to the IP address of each test node server; the virtual machine resource configuration information on each test node server includes but is not limited to the memory size and number of CPU cores allocated to the virtual machine by each test node server.

[0087] Optionally, the task management module running on the management node server obtains a preset configuration file template according to the test kernel type in the configuration information, and fills in the configuration file template based on the root directory address for storing test resources on the test node server, the IP address of each test node server, and the memory size and number of CPU cores allocated to the virtual machine by each test node server, thereby generating a configuration file for the fuzz testing engine.

[0088] S306: Calling test resources through the configuration file of the fuzzy test engine to create a first task process for managing kernel test tasks.

[0089] Optionally, the task management module running on the management node server loads corresponding test resources, such as the test target kernel object and test target disk image of the kernel test task, through the root directory address for storing test resources in the configuration file, thereby creating a first task process for managing the kernel test task.

[0090] In addition, after the task management module calls the test resources through the configuration file of the fuzz testing engine and creates the first task process for managing the kernel testing task, it also synchronizes the task metadata such as the task process identifier (PID, ProcessIDentifier) ​​of the first task process and the creation time of the kernel testing task to the database, so as to implement the stop, resume and other functions of the kernel testing task according to the task process identifier.

[0091] In this embodiment, the task management module running on the management node server calls the test resources through the configuration file of the fuzzy testing engine, automatically creates the first task process for managing the kernel testing tasks, and synchronizes the task metadata of the kernel testing tasks to the database, thereby realizing the automated process of kernel testing task management and effectively improving the efficiency of kernel vulnerability mining.

[0092] S307: Send the test target kernel object and the test target disk image to each test node server.

[0093] The test target kernel object and the test target disk image are used to create a second task process on each test node server.

[0094] Optionally, the task management module running on the management node server sends the test target kernel object and the test target disk image to each test node server, so that each test node server subsequently responds to the test instance creation command and creates a second task process for executing the kernel test task based on the test target kernel object and the test target disk image.

[0095] In this embodiment, the task management module running on the management node server realizes the centralized management and distributed operation of kernel test tasks by sending the test target kernel object and the test target disk image to each test node server. By utilizing the computing resources of each test node server, the computing power of the kernel test is effectively improved, the speed of the kernel test is accelerated, and the efficiency of kernel vulnerability mining is thereby improved.

[0096] S308: Sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command.

[0097] Optionally, the task management module running on the management node server sends a test instance creation command to each test node server through the first task process, so that each test node server responds to the test instance creation command, starts the virtual machine and loads test resources including the test target kernel object and the test target disk image, thereby creating a second task process for executing the kernel test task.

[0098] In addition, the task management module running on the management node server also starts the fuzzy testing engine through the first task process, so that the fuzzy testing engine connects to each test node server according to the address information of each test node server in the configuration file and the virtual machine resource configuration information on each test node server, and generates test cases according to the test case template set and executes them in the virtual machine.

[0099] In this embodiment, an instance creation command is sent to each test node server through the task management module running on the management node to create a second task process. This not only ensures the automated process of the kernel test task, but also makes full use of the computing resources of the test node server, effectively improving the computing power of the kernel test, speeding up the kernel test, and thereby improving the efficiency of kernel vulnerability mining.

[0100] S309: Receive task running data sent by each test node server at a preset time interval.

[0101] Among them, the preset time interval can be set by the user, for example, it can be set to 1 millisecond, 5 minutes, 1 hour, etc. When the preset time interval is set to millisecond level, it can be considered that each test node server uploads the task operation data in real time.

[0102] Optionally, the task management module running on the management node server receives the task running data (ie, the second task process data) sent by each test node server in real time, and centrally manages and stores the received data.

[0103] S310: Synchronize the task running data to the database.

[0104] Optionally, the task management module running on the management node server synchronizes the task running data uploaded by each test node server to the local database, so as to query the task information corresponding to the kernel test task based on the database later. It is worth noting that multiple task processes for managing different kernel test tasks can be run on the management node server at the same time. The task identifier corresponding to each task process at the database level and the task process identifier at the operating system level are different. When the management node server synchronizes the task running data uploaded by each test node server to the local database, it will automatically associate the task running data with the above-mentioned task identifier and task process identifier and store them.

[0105] In this embodiment, the task management module running on the management node server receives the task running data sent by each test node server in real time, and synchronizes the task running data to the database, so as to centrally manage and analyze the task running data of each test node server when executing kernel test tasks. Even if the test node server fails, the data can be restored through the database, which provides efficient and reliable support for kernel vulnerability mining.

[0106] S311: Receive a task information acquisition command sent by a user terminal for a kernel test task.

[0107] The task information acquisition command may be, but is not limited to, a task list acquisition command, a task details acquisition command, etc. The task list acquisition command carries a user identifier, and the task details acquisition command carries a user identifier and a task identifier.

[0108] Optionally, the task management module on the management node server provides the functions of obtaining a task list and obtaining task details. It is understandable that multiple task processes for managing different kernel test tasks can be run simultaneously on the management node server, and the task identifiers corresponding to each task process are different. The management node server can receive a task list acquisition command sent by a user terminal, and obtain all kernel test tasks under the user account and the current running status of each kernel test task from the database through the user identifier carried by the task list acquisition command. In addition, the management node server can also receive a task details acquisition command sent by the user terminal for a specified kernel test task, and query the task details corresponding to the specified kernel test task under the user account from the database through the user identifier and task identifier carried by the task details acquisition command, including the kernel version information of the kernel test task, the task completion status information of the kernel test task, the vulnerability mining status information of the kernel test task, etc.

[0109] S312: In response to the task information acquisition command, the task information of the kernel test task is acquired based on the database.

[0110] The task information includes at least one of the running status information of the kernel test task, the kernel version information of the kernel test task, the task completion status information of the kernel test task, and the vulnerability mining status information of the kernel test task.

[0111] Optionally, the task management module on the management node server responds to the task list acquisition command and obtains all existing kernel test tasks and the running status information of each kernel test task by querying the database. In addition, the task management module on the management node server can also respond to the task detail acquisition command and obtain the task details of the specified kernel test task by querying the database.

[0112] Specifically, the task management module can respond to the task list acquisition command, and obtain all kernel test tasks under the user account and the current running status of each kernel test task from the database through the user identifier carried in the task list acquisition command. In addition, the task management module can also respond to the above-mentioned task details acquisition command, query the database through the user identifier and task identifier carried in the task details acquisition command, and obtain the task details of the specified kernel test task under the user account, including kernel version information, task completion status information of the kernel test task, vulnerability mining status information of the kernel test task, etc.

[0113] S313: Receive a task stop command sent by the user terminal for the kernel test task.

[0114] The task stop command carries a user identifier and a task identifier.

[0115] Optionally, the task management module on the management node server provides a function of stopping the kernel test task. The management node server receives a task stop command sent by a user terminal, searches the database for a task process identifier corresponding to the specified kernel test task through the user identifier and task identifier carried in the task stop command, determines the corresponding second task process on the test node server based on the task process identifier, and pauses these second task processes for executing the kernel test task by sending a pause command to these second task processes. In addition, after pausing the second task process running on each test node server, the task management module also pauses the first task process running on the management node server, thereby pausing the entire specified kernel test task.

[0116] S314: In response to the task stop command, suspend the first task process and the second task process.

[0117] Optionally, the task management module on the management node server responds to the task stop command, searches the database for the task process identifier corresponding to the specified kernel test task through the user identifier and task identifier carried in the task stop command, and determines and suspends the corresponding second task process on the test node server based on the task process identifier. In addition, after suspending the second task process running on each test node server, the task management module also suspends the first task process running on the management node server, thereby suspending the entire specified kernel test task.

[0118] S315: Receive a task recovery command sent by the user terminal for the kernel test task.

[0119] The task recovery command carries a user identifier and a task identifier.

[0120] Optionally, the task management module on the management node server provides a function of stopping the kernel test task. The management node server receives a task recovery command sent by the user terminal, and recovers the first task process running on the management node server through the user identifier and task identifier carried in the task recovery command. The task process identifier corresponding to the specified kernel test task is searched in the database, and the second task processes for executing the kernel test task are determined and recovered based on the task process identifier.

[0121] S316: In response to the task resumption command, resume the first task process and the second task process.

[0122] Optionally, in response to the task recovery command, the task management module on the management node server searches the database for the task process identifier corresponding to the specified kernel test task through the user identifier and task identifier carried in the task recovery command, and recovers the first task process running on the management node server. The task process identifier corresponding to the specified kernel test task is searched in the database, and the second task processes for executing the kernel test task are determined and recovered based on the task process identifier.

[0123] In this embodiment, the task management module on the management node server provides the function of automatically stopping and resuming tasks, and can realize automatic task suspension and task resumption without human intervention, which effectively improves the efficiency of kernel vulnerability mining.

[0124] S317: When it is detected through the polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number, the first task process and the second task process are terminated.

[0125] Optionally, the task management module on the management node server provides a function of automatically terminating the kernel test task. It is understandable that multiple task processes for managing different kernel test tasks can be run simultaneously on the management node server. The task management module can detect whether all currently running kernel test tasks meet the preset termination conditions by creating a polling thread, that is, detect whether the test duration of all currently running kernel test tasks reaches the test target duration, or whether the number of test crashes reaches the test target crash number. When it is detected through the polling thread that the test duration of the kernel test task reaches the test target duration or the number of test crashes of the kernel test task reaches the test target crash number, the kernel test task that meets the preset termination conditions is automatically terminated, that is, the first task process of the kernel test task on the management node server and the second task process on the test node server are terminated.

[0126] In this embodiment, the task management module running on the management node server automatically ends the first task process and the second task process when it detects through the polling thread that the kernel test task meets the preset termination conditions, thereby improving the automation level of kernel test task management and terminating the kernel test task in a timely manner without human monitoring.

[0127] S318: Storing the kernel test data of the kernel test task to a preset storage path.

[0128] The kernel test data includes, but is not limited to, information related to the test kernel crash, coverage information (such as kernel code coverage information), kernel log information, etc.

[0129] Optionally, the task management module running on the management node server provides an information synchronization function after automatically ending the kernel test task. Specifically, after ending the first task process and the second task process of the kernel test task, the task management module running on the management node server stores the kernel test data uploaded by each test node server at a preset time interval, including relevant information of the test kernel crash, kernel code coverage information, kernel log information, etc., to a preset storage path on the management node server, such as a preset task-specific directory on the management node server.

[0130] S319: Storing the kernel test corpus of the kernel test task into the database.

[0131] The kernel test corpus includes, but is not limited to, the corpus corresponding to each test case in the test case template set, the corpus newly discovered by the fuzzy test engine in the process of executing the kernel test task, etc.

[0132] Optionally, the task management module running on the management node server also provides a corpus merging function after automatically ending the kernel test task. Specifically, after ending the first task process and the second task process of the kernel test task, the task management module running on the management node server merges and stores the corpus corresponding to each test case in the test case template set, the corpus newly discovered by the fuzzy test engine during the execution of the kernel test task, etc. into a local database.

[0133] It is worth noting that after synchronizing the kernel test data and merging the kernel test corpus, the task management module also clears the test resources originally stored in each test node server and the management node server, thereby giving up computing resources without losing corpus information.

[0134] In this embodiment, after the kernel test task is completed, the task management module running on the management node server provides information synchronization and corpus merging functions, that is, all kernel test data collected during the test (such as relevant information on the test kernel crash, etc.) are stored in a preset storage path, and the generated test corpus (such as the corpus newly discovered by the fuzz test engine during the execution of the kernel test task, etc.) is merged and uploaded to the database. In addition, the task management module will also clean up and release the used resources. In the above manner, not only can the corpus information generated during the kernel test process be automatically saved, but also unnecessary resources can be cleaned up in time, and the corpus information can be not lost while giving up computing resources, which effectively improves the efficiency of kernel vulnerability mining.

[0135] See also Figure 4, which is a schematic diagram of the architecture of the kernel test task management method. The user interacts with the task management module running on the management node server (such as HTTP server) through the Web UI interface of the user terminal, and implements kernel test task management based on the browser / server (B / S) architecture. Specifically, the task management module running on the management node server can provide functions such as automatically creating kernel test tasks, automatically stopping kernel test tasks, resuming kernel test tasks, ending kernel test tasks, obtaining kernel test task lists, and obtaining kernel test task details. Through the B / S architecture, the user can conveniently interact with the task management module on the management node server through the browser to implement the management and control of kernel test tasks.

[0136] The above-mentioned kernel test task management method is applied to the management node server. By determining the test resources of the kernel test task according to the configuration information sent by the user terminal, configuring the test environment based on the test resources, and automatically creating a first task process for managing the kernel test task, manual intervention is reduced and the kernel test preparation time is shortened; through the first task process, a test instance creation command is sent to at least one test node server, so that each test node server automatically creates a second task process for executing the kernel test task based on the test instance creation command, which can not only ensure the automation process of the kernel test task, but also make full use of the computing resources of the test node server, effectively improve the computing power of the kernel test, and speed up the kernel test; when it is detected through the polling thread that the kernel test task meets the preset termination condition, the first task process and the second task process are automatically terminated, which improves the automation level of kernel test task management and can terminate the kernel test task in time without manual monitoring. In addition, during the execution of the kernel test task, the task management module can also respond to commands issued by the user terminal to pause the kernel test task, resume the kernel test task, obtain the kernel test task list and obtain the kernel test task details in real time; after completing the kernel test task, the task management module can also synchronize information and merge corpora, and clean up and release the used resources in time, so as to give up computing resources without losing coverage information.

[0137] The entire kernel test task management process adopts centralized management and distributed execution, and realizes automatic management of kernel test tasks based on B / S architecture. It automatically creates and terminates kernel test tasks, responds to commands issued by user terminals in real time during the execution of kernel test tasks, and performs information synchronization, corpus merging and resource cleanup after the kernel test is completed. It can make full use of the computing resources of the test node server, thereby effectively improving the efficiency of kernel vulnerability mining and facilitating large-scale kernel vulnerability mining.

[0138] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0139] Based on the invention concept of the kernel test task management method, Figure 5 As shown, the embodiment of the present application also provides a kernel test task management device 500 for implementing the kernel test task management method involved above. The kernel test task management device 500 includes:

[0140] The resource determination module 501 is used to determine the test resources of the kernel test task according to the configuration information sent by the user terminal;

[0141] A first creation module 502, used to create a first task process for managing kernel test tasks based on test resources;

[0142] A second creation module 503 is used to send a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command;

[0143] The task ending module 504 is used to end the first task process and the second task process when it is detected through the polling thread that the kernel test task meets the preset ending condition.

[0144] In one possible implementation, the configuration information includes a test kernel type, a test kernel version number, and a test case template library; the resource determination module 501 is specifically used to determine the test target kernel object and the test target disk image of the kernel test task according to the test kernel type and the test kernel version number; determine the test case template set of the kernel test task according to the test case template library; determine the fuzzy test engine of the kernel test task according to the test kernel type, the test kernel version number, and the test case template library.

[0145] In one possible implementation, the configuration information includes storage path information of test resources, address information of each test node server, and virtual machine resource configuration information on each test node server; the first creation module 502 is also used to generate a configuration file for the fuzzy testing engine based on the storage path information of the test resources, the address information of each test node server, and the virtual machine resource configuration information on each test node server; the test resources are called through the configuration file of the fuzzy testing engine to create a first task process for managing kernel test tasks.

[0146] In a possible implementation, the second creation module 503 is further used to send the test target kernel object and the test target disk image to each test node server; the test target kernel object and the test target disk image are used to create a second task process in each test node server.

[0147] In one possible implementation, the configuration information includes a test target duration and a test target crash number; the task end module 504 is specifically used to end the first task process and the second task process when it is detected through a polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number.

[0148] In one possible implementation, the kernel test task management device 500 also includes a task stop module and a task recovery module. The task stop module is used to receive a task stop command sent by the user terminal for the kernel test task, and in response to the task stop command, suspend the first task process and the second task process; the task recovery module is used to receive a task recovery command sent by the user terminal for the kernel test task; and in response to the task recovery command, resume the first task process and the second task process.

[0149] In a possible implementation, the kernel test task management device 500 further includes a data synchronization module for receiving task execution data sent by each test node server at a preset time interval; and synchronizing the task execution data to a database.

[0150] In one possible implementation, the kernel test task management device 500 also includes a task information acquisition module, which is used to receive a task information acquisition command sent by a user terminal for a kernel test task; in response to the task information acquisition command, the task information of the kernel test task is acquired based on a database; the task information includes at least one of the running status information of the kernel test task, the kernel version information of the kernel test task, the task completion status information of the kernel test task, and the vulnerability mining status information of the kernel test task.

[0151] In a possible implementation, the kernel test task management device 500 further includes a data storage module for storing the kernel test data of the kernel test task in a preset storage path; and storing the kernel test corpus of the kernel test task in a database.

[0152] Each module in the kernel test task management device 500 can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0153] The embodiment of the present application also provides an electronic device, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown. The electronic device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the electronic device is used to store kernel test task data. The input / output interface of the electronic device is used to exchange information between the processor and an external device. The communication interface of the electronic device is used to communicate with an external terminal through a network connection. The processor of the electronic device executes a computer program to implement a method for generating a server image.

[0154] Those skilled in the art will understand that Figure 6 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the electronic device to which the scheme of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] In a possible implementation, an electronic device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0156] Determine the test resources for the kernel test task according to the configuration information sent by the user terminal;

[0157] Based on the test resources, create a first task process for managing the kernel test task;

[0158] Sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command;

[0159] When it is detected through the polling thread that the kernel test task meets the preset termination condition, the first task process and the second task process are terminated.

[0160] In one possible implementation, the configuration information includes a test kernel type, a test kernel version number, and a test case template library; when the processor executes the computer program, the following steps are also implemented: based on the test kernel type and the test kernel version number, the test target kernel object and the test target disk image of the kernel test task are determined; based on the test case template library, the test case template set of the kernel test task is determined; based on the test kernel type, the test kernel version number, and the test case template library, the fuzzy test engine of the kernel test task is determined.

[0161] In one possible implementation, the configuration information includes storage path information of test resources, address information of each test node server, and virtual machine resource configuration information on each test node server; when the processor executes the computer program, the following steps are also implemented: based on the storage path information of test resources, the address information of each test node server, and the virtual machine resource configuration information on each test node server, a configuration file of the fuzzy test engine is generated; the test resources are called through the configuration file of the fuzzy test engine, and a first task process for managing kernel test tasks is created.

[0162] In a possible implementation, the processor further implements the following steps when executing the computer program: sending the test target kernel object and the test target disk image to each test node server; and using the test target kernel object and the test target disk image to create a second task process in each test node server.

[0163] In one possible implementation, the configuration information includes a test target duration and a test target crash number; when the processor executes the computer program, the following steps are also implemented: when it is detected through a polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number, the first task process and the second task process are terminated.

[0164] In one possible implementation, the processor also implements the following steps when executing the computer program: receiving a task stop command sent by the user terminal for the kernel test task; pausing the first task process and the second task process in response to the task stop command; receiving a task resume command sent by the user terminal for the kernel test task; and resuming the first task process and the second task process in response to the task resume command.

[0165] In a possible implementation, when the processor executes the computer program, it also implements the following steps: receiving task execution data sent by each test node server at a preset time interval; and synchronizing the task execution data to a database.

[0166] In one possible implementation, the processor also implements the following steps when executing the computer program: receiving a task information acquisition command sent by a user terminal for a kernel test task; in response to the task information acquisition command, acquiring task information of the kernel test task based on a database; the task information includes at least one of the running status information of the kernel test task, the kernel version information of the kernel test task, the task completion status information of the kernel test task, and the vulnerability mining status information of the kernel test task.

[0167] In a possible implementation, when the processor executes the computer program, it further implements the following steps: storing the kernel test data of the kernel test task to a preset storage path; and storing the kernel test corpus of the kernel test task to a database.

[0168] The present application also provides a computer storage medium, which stores instructions, and when the instructions are executed on a computer or a processor, the computer or the processor executes one or more steps in the above embodiment. If the components of the above electronic device are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer readable storage medium.

[0169] In a possible implementation, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0170] Determine the test resources for the kernel test task according to the configuration information sent by the user terminal;

[0171] Based on the test resources, create a first task process for managing the kernel test task;

[0172] Sending a test instance creation command to at least one test node server through the first task process, so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command;

[0173] When it is detected through the polling thread that the kernel test task meets the preset termination condition, the first task process and the second task process are terminated.

[0174] In one possible implementation, the configuration information includes a test kernel type, a test kernel version number, and a test case template library; when the computer program is executed by a processor, the following steps are also implemented: based on the test kernel type and the test kernel version number, a test target kernel object and a test target disk image of the kernel test task are determined; based on the test case template library, a test case template set of the kernel test task is determined; based on the test kernel type, the test kernel version number, and the test case template library, a fuzzy test engine of the kernel test task is determined.

[0175] In one possible implementation, the configuration information includes storage path information of test resources, address information of each test node server, and virtual machine resource configuration information on each test node server; when the computer program is executed by the processor, the following steps are also implemented: based on the storage path information of test resources, the address information of each test node server, and the virtual machine resource configuration information on each test node server, a configuration file of the fuzzy test engine is generated; the test resources are called through the configuration file of the fuzzy test engine to create a first task process for managing kernel test tasks.

[0176] In one possible implementation, when the computer program is executed by the processor, the following steps are also implemented: sending the test target kernel object and the test target disk image to each test node server; the test target kernel object and the test target disk image are used to create a second task process in each test node server.

[0177] In one possible implementation, the configuration information includes a test target duration and a test target crash number; when the computer program is executed by a processor, the following steps are also implemented: when it is detected through a polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number, the first task process and the second task process are terminated.

[0178] In one possible implementation, when the computer program is executed by the processor, the following steps are also implemented: receiving a task stop command sent by the user terminal for the kernel test task; suspending the first task process and the second task process in response to the task stop command; receiving a task resume command sent by the user terminal for the kernel test task; and resuming the first task process and the second task process in response to the task resume command.

[0179] In a possible implementation, when the computer program is executed by the processor, the following steps are also implemented: receiving task execution data sent by each test node server at a preset time interval; and synchronizing the task execution data to a database.

[0180] In one possible implementation, when the computer program is executed by the processor, the following steps are also implemented: receiving a task information acquisition command sent by a user terminal for a kernel test task; in response to the task information acquisition command, acquiring task information of the kernel test task based on a database; the task information includes at least one of the running status information of the kernel test task, the kernel version information of the kernel test task, the task completion status information of the kernel test task, and the vulnerability mining status information of the kernel test task.

[0181] In a possible implementation, when the computer program is executed by the processor, the following steps are also implemented: storing the kernel test data of the kernel test task to a preset storage path; and storing the kernel test corpus of the kernel test task to a database.

[0182] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer storage medium or transmitted through the computer storage medium. The computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0183] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other media that can store program codes. In the absence of conflict, the technical features in this embodiment and the implementation scheme can be combined arbitrarily.

[0184] The embodiments described above are merely preferred embodiments of the present application and are not intended to limit the scope of the present application. Without departing from the design spirit of the present application, various modifications and improvements made to the technical solutions of the present application by ordinary technicians in this field should fall within the protection scope determined by the claims.

[0185] The above describes a specific embodiment of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A kernel test task management method, characterized in that: Applied to a management node server, the method comprises: Determine the test resources for the kernel test task according to the configuration information sent by the user terminal; Based on the test resources, create a first task process for managing the kernel test task; Sending a test instance creation command to at least one test node server through the first task process, so that each of the test node servers creates a second task process for executing the kernel test task based on the test instance creation command; When it is detected through the polling thread that the kernel test task meets a preset termination condition, the first task process and the second task process are terminated.

2. The method according to claim 1, characterized in that The configuration information includes the test kernel type, the test kernel version number and the test case template library; The step of determining the test resources of the kernel test task according to the configuration information sent by the user terminal includes: Determine the test target kernel object and the test target disk image of the kernel test task according to the test kernel type and the test kernel version number; Determine a test case template set for the kernel test task according to the test case template library; The fuzzy test engine of the kernel test task is determined according to the test kernel type, the test kernel version number and the test case template library.

3. The method according to claim 1, characterized in that The configuration information includes storage path information of the test resources, address information of each of the test node servers, and virtual machine resource configuration information on each of the test node servers; Before creating a first task process for managing the kernel test task based on the test resource, the method further includes: Generate a configuration file of a fuzzy test engine based on the storage path information of the test resources, the address information of each of the test node servers, and the virtual machine resource configuration information on each of the test node servers; The step of creating a first task process for managing the kernel test task based on the test resource includes: The test resource is called through the configuration file of the fuzz test engine to create a first task process for managing the kernel test task.

4. The method according to claim 2, characterized in that Before sending a test instance creation command to at least one test node server through the first task process so that each test node server creates a second task process for executing the kernel test task based on the test instance creation command, the method further includes: The test target kernel object and the test target disk image are sent to each of the test node servers; the test target kernel object and the test target disk image are used to create the second task process in each of the test node servers.

5. The method according to claim 1, characterized in that The configuration information includes the test target duration and the number of test target crashes; The step of terminating the first task process and the second task process when detecting through the polling thread that the kernel test task satisfies a preset termination condition comprises: When it is detected through the polling thread that the test duration of the kernel test task reaches the test target duration or the test crash number of the kernel test task reaches the test target crash number, the first task process and the second task process are terminated.

6. The method according to claim 1, characterized in that The method further comprises: Receiving a task stop command sent by the user terminal for the kernel test task; In response to the task stop command, pausing the first task process and the second task process; receiving a task recovery command sent by the user terminal for the kernel test task; In response to the task resumption command, the first task process and the second task process are resumed.

7. The method according to claim 1, characterized in that In the case where it is detected through the polling thread that the kernel test task satisfies a preset termination condition, before terminating the first task process and the second task process, the method further includes: Receive task running data sent by each test node server at a preset time interval; The task execution data is synchronized to the database.

8. A kernel test task management device, characterized in that: Applied to a management node server, the device comprises: A resource determination module, used to determine the test resources of the kernel test task according to the configuration information sent by the user terminal; A first creation module, used for creating a first task process for managing the kernel test task based on the test resource; A second creation module, used to send a test instance creation command to at least one test node server through the first task process, so that each of the test node servers creates a second task process for executing the kernel test task based on the test instance creation command; The task ending module is used to end the first task process and the second task process when it is detected through the polling thread that the kernel test task meets the preset ending condition.

9. An electronic device, characterized in that: include: A processor and a memory; the memory stores a computer program, and the processor implements the method steps of any one of claims 1 to 7 when executing the computer program.

10. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.