WO2021164165A1

WO2021164165A1 - File lock processing method and apparatus, electronic device, and storage medium

Info

Publication number: WO2021164165A1
Application number: PCT/CN2020/098005
Authority: WO
Inventors: 臧林劼; 何营
Original assignee: 苏州浪潮智能科技有限公司
Priority date: 2020-02-20
Filing date: 2020-06-24
Publication date: 2021-08-26
Also published as: CN111274214B; CN111274214A

Abstract

Provided are a file lock processing method and apparatus, an electronic device, and a computer-readable storage medium. The method comprises: acquiring a blocking lock chain table of a target file system, wherein the blocking lock chain table comprises all file lock requests of the target file system that are suspended at present; determining whether the target file system supports an asynchronous blocking lock; if not, determining, according to the request type of each file lock request, a file lock state corresponding to each file lock request, wherein the file lock state comprises a non-blocking lock state and a blocking lock polling state; and returning a blocking state to a client initiating a target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded to by a server, wherein the target file lock request is a file lock request, the file lock state of which is the blocking lock polling state. By means of the file lock processing method provided in the present application, the maintainability of file lock management in a file system is improved.

Description

File lock processing method, device, electronic equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 202010105189.6, and the invention title is "a file lock processing method, device, electronic equipment and storage medium" on February 20, 2020, and its entire content Incorporated in this application by reference.

Technical field

This application relates to the field of computer technology, and more specifically, to a file lock processing method and device, an electronic device, and a computer-readable storage medium.

Background technique

In the mass storage business, users have higher and higher requirements for data transmission performance and stability. The storage server will have a huge number of clients, and multiple clients will access files on the server at the same time, which will inevitably cause file conflicts. Collaboration between terminals and ensuring the consistency of file data have become the focus of software users and developers.

File lock is a mechanism to achieve file synchronization in multitasking operation scenarios, ensuring file data consistency and preventing conflicts. If a process tries to write to a file that is being read by other processes, it may cause a read operation The process reads some corrupted or incomplete data. If two processes write to the same file concurrently, the file may be damaged. Therefore, in order to avoid this kind of problem, a mechanism must be adopted to solve the synchronization problem faced by multiple processes concurrently accessing the same file, resulting in file locking technology.

Asynchronous blocking lock means that the client initiates a lock request, the current thread is suspended, and if the file is occupied, it waits until the call returns, sending a Granged message to the client that sent the lock request to authorize the lock. In a distributed file system application scenario, if the file system does not support asynchronous blocking locks, the client will wait forever, and the maintainability of file locks is poor.

Therefore, how to improve the maintainability of the file lock in the file system is a technical problem that needs to be solved by those skilled in the art.

Summary of the invention

The purpose of this application is to provide a file lock processing method and device, an electronic device, and a computer-readable storage medium to improve the maintainability of the file lock in the file system.

In order to achieve the above objective, this application provides a file lock processing method applied to a server, including:

Acquiring a blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

Determine whether the target file system supports asynchronous blocking locks;

If not, determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes a non-blocking lock state and a polling blocking lock state;

The blocking state is returned to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server, wherein the target file The lock request is a file lock request whose file lock state is the polling blocking lock state.

Wherein, the obtaining the blocking chain list of the target file system includes:

When receiving a file lock request from the target client for the target file in the target file system, obtain the block chain list of the target file system.

Among them, it also includes:

When the target file system supports asynchronous blocking locks, if the file lock request is a read request for the target file, the file lock state corresponding to the file lock request is determined to be the non-blocking lock state; if If the file lock request includes a write request to the target file, the file lock state corresponding to the file lock request is determined to be an asynchronous blocking lock state.

Obtain the blocking chain list of the target file system every preset time interval.

Wherein, the determining the file lock status corresponding to each file lock request according to the request type of each file lock request includes:

If the file lock request is a read request for the target file, determining the file lock state corresponding to the file lock request as the non-blocking lock state;

If the file lock request includes a write request for the target file, the file lock state corresponding to the file lock request is determined as the polling block lock state.

Create a thread pool, and use the target thread in the thread pool to traverse the blocking chain list, so as to determine the file corresponding to each file lock request in the blocking chain table according to the request type of each file lock request Lock state.

In order to achieve the above objective, the present application provides a file lock processing device, including:

An obtaining module, configured to obtain a blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

The judging module is used to judge whether the target file system supports asynchronous blocking lock; if not, start the work flow of the first determining module;

The first determining module is configured to determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes a non-blocking lock state and a polling block Lock status

The return module is used to return the blocking state to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server, wherein , The target file lock request is a file lock request whose file lock state is the polling block lock state.

Wherein, the obtaining module is specifically a module that obtains the blocking chain list of the target file system when a file lock request of the target file in the target file system is received by the target client.

In order to achieve the above objective, this application provides an electronic device, including:

Memory, used to store computer programs;

The processor is used to implement the steps of the file lock processing method when the computer program is executed.

To achieve the foregoing objective, the present application provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the file lock processing method described above are implemented.

It can be seen from the above solution that the file lock processing method provided by the present application includes: obtaining a block chain list of the target file system; wherein the block chain list includes all file locks currently suspended in the target file system. Request; determine whether the target file system supports asynchronous blocking locks; if not, determine the file lock status corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock status includes unblocked Block lock status and polling block lock status; return the blocking status to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is blocked The server responds, wherein the target file lock request is a file lock request whose file lock state is the polling block lock state.

In the file lock processing method provided by this application, when the target file system does not support asynchronous blocking locks, the corresponding file lock status is determined based on the request type of each file lock request, so that all file lock requests in the blocked lock chain are filed. Recognition of lock status. The blocking state is returned to the client that initiated the file lock request polling the blocking lock state, and the client re-initiates the file lock request at a preset time after receiving the blocking state, until the file lock request is responded by the server. It can be seen that the file lock processing method provided by the present application improves the maintainability of file lock management in the file system by identifying the file lock status, and ensures the high consistency of files in concurrent services. The application also discloses a file lock processing device, an electronic device and a computer-readable storage medium, which can also achieve the above technical effects.

It should be understood that the above general description and the following detailed description are only exemplary and cannot limit the application.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the present disclosure, but do not constitute a limitation to the present disclosure. In the attached picture:

Fig. 1 is a flow chart showing a file lock processing method according to an exemplary embodiment;

Fig. 2 is a flowchart showing another file lock processing method according to an exemplary embodiment;

Figure 3 is an architecture diagram of the NFS-Ganesha file lock request processing flow;

Figure 4 is a process flow chart of the method for identifying asynchronous blocked file locks by polling

Fig. 5 is a structural diagram of a file lock processing device according to an exemplary embodiment;

Fig. 6 is a structural diagram of an electronic device according to an exemplary embodiment.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The embodiment of the present application discloses a file lock processing method, which improves the maintainability of the file lock in the file system.

Referring to Fig. 1, a flowchart of a method for processing a file lock according to an exemplary embodiment, as shown in Fig. 1, includes:

S101: Obtain a blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

The target file system in this embodiment is a distributed file system, such as the NFS-Ganesha user-mode network file system, which can manage millions of data caches, avoiding the problem of blocking the underlying file system, and NFS-Ganesha has a flexible internal allocation mechanism , User mode program can allocate a large amount of memory for internal use of the program, effectively solving the problem of data caching. NFS-Ganesha can interface with a variety of underlying distributed file systems. The FSAL (File System Abstraction Layer) file system abstraction layer is a very important module. FSAL itself provides a common interface for Inode Cache and File Content Cache, which will be called after receiving the request. Specific FSAL, such as virtual file system (VFS), distributed file system, etc.

In specific implementation, when a file lock request for a file in the target file system is received from the client, when the file lock is in the file lock state and the file lock is in a non-blocking lock state, the file lock request is suspended, that is, the file lock request is suspended. The file lock request is added to the blocking chain list. In other words, the blocking chain list of the target file system stores all file lock requests that are currently suspended.

It should be noted that this embodiment does not limit the trigger condition of this step. For example, when a file lock request of a target file in the target file system is received by a target client, the block chain list of the target file system is acquired . For another example, the block chain list of the target file system is obtained at preset time intervals.

S102: Determine whether the target file system supports asynchronous blocking lock; if not, go to S103;

When the target file system supports asynchronous blocking lock, if the file requested by the client already has a file lock and the file lock is in the non-blocking lock state, it directly responds to the file lock request of the client, otherwise the file lock request is in the blocking lock state The flag bit asynchronously blocks the lock state. Asynchronous blocking lock means that the client initiates a lock request, the current thread is suspended, and if the file is occupied, it waits until the call returns, sending a Granged message to the client that sent the lock request to authorize the lock.

S103: Determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes a non-blocking lock state and a polling blocking lock state;

When the target file system does not support asynchronous blocking locks, the corresponding file lock status can be determined according to the request type of the file lock request. File lock status includes non-blocking lock status and polling blocking lock status. Non-blocking lock status means that the client initiates a lock request. The current thread will not be suspended, but will immediately return to execute the next call. If the file is occupied, immediately return. The blocking lock state means that the NFS client initiates a lock request, the current thread is suspended, and waits if the file is occupied. Polling blocking lock status means that the client initiates a lock request every preset time until the lock request is responded.

In this step, you can define the blocking lock polling function. First, create a union to identify four blocking lock states, including non-blocking lock state STATE_BLOCK_NONE, blocking lock state STATE_BLOCK_INTERNAL, asynchronous blocking lock state STATE_BLOCK_ASYNC, and polling blocking lock state STATE_BLOCK_POLL. The specific structure is as follows:

As a preferred embodiment, this step includes: creating a thread pool, and using the target thread in the thread pool to traverse the blocking chain list, so as to determine the blocking chain list according to the request type of each file lock request The file lock status corresponding to each of the file lock requests in. In the specific implementation, the polling thread is built, the thread pool is initialized, and the thread parameters are set. In the polling scenario, in order to avoid wasting system resources, set the maximum/minimum number of threads in the thread pool to 1, and set the polling thread Time interval, set the calling rules of the polling thread processing process. The above polling thread time interval is a thread time interval variable, ranging from 0 to 180s, and the default polling time is 10s. The polling thread calling rule means that the polling thread cyclically blocks the lock polling function. The function of the blocking lock polling function is to poll all the blocking locks of type STATE_BLOCK_POLL, and loop through the blocking locks of type STATE_BLOCK_POLL in the double-linked list of blocking locks.

S104: Return a blocking state to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded to by the server, where the The target file lock request is a file lock request whose file lock state is the polling blocking lock state.

In this step, the blocking state is returned to the client that initiated the file lock request polling the blocking lock state, and the client re-initiates the file lock request every preset time after receiving the blocking state, until the file lock request is responded by the server. It can be seen that when the file system does not support asynchronous blocking locks and the client initiates an asynchronous blocking lock request, the return status is marked as blocked. The purpose is to prevent file lock conflicts from unclear recognition of the file lock status and confusion to prevent The file lock status is misjudged.

In the file lock processing method provided by the embodiments of the present application, when the target file system does not support asynchronous blocking locks, the corresponding file lock status is determined based on the request type of each file lock request, and all file lock requests in the blocked lock chain are realized. Perform file lock status recognition. The blocking state is returned to the client that initiated the file lock request polling the blocking lock state, and the client re-initiates the file lock request at a preset time after receiving the blocking state, until the file lock request is responded by the server. It can be seen that the file lock processing method provided by the embodiment of the present application improves the maintainability of file lock management in the file system by identifying the file lock status, and ensures the high consistency of files in concurrent services.

The embodiment of the application discloses a file lock processing method. Compared with the previous embodiment, this embodiment further illustrates and optimizes the technical solution. specific:

Referring to FIG. 2, a flowchart of another file lock processing method according to an exemplary embodiment, as shown in FIG. 2, includes:

S201: When a file lock request of a target file in the target file system is received by a target client, acquire a block chain list of the target file system;

S202: Determine whether the target file system supports asynchronous blocking locks; if yes, go to S203; if not, go to S204;

S203: If the file lock request is a read request for the target file, determine the file lock state corresponding to the file lock request as the non-blocking lock state; if the file lock request includes the target file For a file write request, the file lock state corresponding to the file lock request is determined to be an asynchronous blocking lock state;

S204: Create a thread pool, and use the target thread in the thread pool to traverse the blocking chain list;

S205: If the file lock request is a read request for the target file, determine the file lock state corresponding to the file lock request as the non-blocking lock state; if the file lock request includes the target file For a file write request, the file lock state corresponding to the file lock request is determined as the polling blocking lock state.

In a specific implementation, if the client requests a write request for a target file, an exclusive lock needs to be allocated to the client due to operations such as modification of the target file. If the target file already has an exclusive lock of another client at this time, the file lock state corresponding to the file lock request needs to be marked as the polling blocking lock state, so that the client can poll and send the file lock request in the subsequent steps until it is responded.

S206: Return a blocking state to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server.

It can be seen that the construction thread of this embodiment polls the blocking chain list, realizes the marking of the file lock status of the file lock request, improves the maintainability of the file lock management in the network file system, and ensures that the file is in the concurrent business. Is highly consistent.

The following introduces an application embodiment provided by the present application. Specifically, FIG. 3 is an architecture diagram of an NFS-Ganesha file lock request processing flow, and FIG. 4 is a processing flowchart of a method for identifying an asynchronously blocked file lock by polling.

For the case where different clients successively initiate read operations on the same file, the NFS file lock request is defined as a shared read lock. Since the client does not perform a write operation, the file lock state that marks the file lock request is a non-blocking lock state.

For the case where different clients successively initiate write operations to the same file, the NFS file lock request is defined as an exclusive write lock. Due to operations such as modifying the file, it is a blocking lock. When one client has a write lock, the other client has a write lock. Waiting. At this time, it is in a blocking state. After receiving the blocking instruction, the server performs two processing: The first is that the underlying distributed file system supports asynchronous blocking locks. When the first client releases the lock, the server actively informs the client The end lock is released, and the second client in the blocked state can be authorized to lock. The second type is that when the distributed file system does not support asynchronous blocking locks, the server performs polling and the client passively waits for authorization to realize the asynchronous blocking function of multiple clients.

For the case where different clients successively initiate read and write operations on the same file, since it includes write operations, it is also an exclusive lock, which is similar to the above situation and will not be repeated here. In the case where different clients successively initiate read and write operations on different files, the operations on different files do not affect each other.

The following describes a file lock processing device provided by an embodiment of the present application. The file lock processing device described below and the file lock processing method described above can refer to each other.

Referring to FIG. 5, a structural diagram of a file lock processing device according to an exemplary embodiment, as shown in FIG. 5, includes:

The obtaining module 501 is configured to obtain the blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

The judging module 502 is used to judge whether the target file system supports asynchronous blocking lock; if not, start the work flow of the first determining module 503;

The first determining module 503 is configured to determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes non-blocking lock state and polling Blocking lock state;

The return module 504 is configured to return a blocking state to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server, Wherein, the target file lock request is a file lock request whose file lock state is the polling block lock state.

In the file lock processing device provided by the embodiment of the present application, when the target file system does not support asynchronous blocking locks, the corresponding file lock status is determined based on the request type of each file lock request, so as to realize all file lock requests in the blocked lock chain. Perform file lock status recognition. The blocking state is returned to the client that initiated the file lock request polling the blocking lock state, and the client re-initiates the file lock request at a preset time after receiving the blocking state, until the file lock request is responded by the server. It can be seen that the file lock processing device provided by the embodiment of the present application improves the maintainability of the file lock management in the file system by identifying the file lock status, and ensures the high consistency of files in concurrent services.

On the basis of the foregoing embodiment, as a preferred implementation, the acquiring module 501 is specifically configured to acquire the file lock request of the target file system from the target client when it receives a file lock request for the target file in the target file system. Block the module of the chain list.

On the basis of the foregoing embodiment, as a preferred implementation manner, it further includes:

The second determining module is configured to determine that the file lock status corresponding to the file lock request is the file lock status corresponding to the file lock request if the file lock request is a read request for the target file when the target file system supports asynchronous blocking locks. The non-blocking lock state; if the file lock request includes a write request to the target file, the file lock state corresponding to the file lock request is determined to be an asynchronous blocking lock state.

On the basis of the foregoing embodiment, as a preferred implementation manner, the acquiring module 501 is specifically a module that acquires the blocking chain list of the target file system at predetermined time intervals.

On the basis of the foregoing embodiment, as a preferred implementation manner, the first determining module 503 includes:

A first determining unit, configured to determine the file lock state corresponding to the file lock request as the non-blocking lock state if the file lock request is a read request for the target file;

The second determining unit is configured to, if the file lock request includes a write request to the target file, determine the file lock state corresponding to the file lock request as the polling block lock state.

On the basis of the foregoing embodiment, as a preferred implementation manner, the first determining module 503 specifically creates a thread pool, and uses the target thread in the thread pool to traverse the blocking chain list, so that according to each The request type of the file lock request determines the module of the file lock state corresponding to each file lock request in the blocked lock chain table.

Regarding the device in the foregoing embodiment, the specific manner in which each module performs operation has been described in detail in the embodiment of the method, and detailed description will not be given here.

The present application also provides an electronic device. Referring to FIG. 6, a structural diagram of an electronic device 600 provided in an embodiment of the present application, as shown in FIG. 6, may include a processor 11 and a memory 12. The electronic device 600 may also include one or more of a multimedia component 13, an input/output (I/O) interface 14, and a communication component 15.

The processor 11 is used to control the overall operation of the electronic device 600 to complete all or part of the steps in the file lock processing method described above. The memory 12 is used to store various types of data to support operations on the electronic device 600. These data may include, for example, instructions for any application or method to operate on the electronic device 600, as well as application-related data. For example, contact data, messages sent and received, pictures, audio, video, etc. The memory 12 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random Access Memory, SRAM for short), electrically erasable programmable read-only memory ( Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-only Memory (Read-Only Memory, ROM for short), magnetic memory, flash memory, magnetic disk or optical disk. The multimedia component 13 may include a screen and an audio component. The screen may be a touch screen, for example, and the audio component is used to output and/or input audio signals. For example, the audio component may include a microphone, which is used to receive external audio signals. The received audio signal may be further stored in the memory 12 or transmitted through the communication module 15. The audio component also includes at least one speaker for outputting audio signals. The I/O interface 14 provides an interface between the processor 11 and other interface modules. The above-mentioned other interface modules may be a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons. The communication component 15 is used for wired or wireless communication between the electronic device 600 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination of one or more of them, so the corresponding communication component 15 may include: Wi-Fi module, Bluetooth module, NFC module.

In an exemplary embodiment, the electronic device 600 may be used by one or more application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), digital signal processor (Digital Signal Processor, DSP for short), and digital signal processing equipment (Digital Signal Processor for short). Signal Processing Device, DSPD for short), Programmable Logic Device (PLD for short), Field Programmable Gate Array (FPGA for short), controller, microcontroller, microprocessor or other electronic components Implementation, used to execute the above-mentioned file lock processing method.

In another exemplary embodiment, there is also provided a computer-readable storage medium including program instructions, which implement the steps of the file lock processing method described above when the program instructions are executed by a processor. For example, the computer-readable storage medium may be the foregoing memory 12 including program instructions, and the foregoing program instructions may be executed by the processor 11 of the electronic device 600 to complete the foregoing file lock processing method.

The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method part. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of this application, several improvements and modifications can be made to this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

It should also be noted that in this specification, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is any such actual relationship or sequence between operations. Moreover, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes those that are not explicitly listed Other elements of, or also include elements inherent to this process, method, article or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other same elements in the process, method, article, or equipment that includes the element.

Claims

A file lock processing method, which is characterized in that it is applied to a server and includes:

Acquiring a blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

Determine whether the target file system supports asynchronous blocking locks;

If not, determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes a non-blocking lock state and a polling blocking lock state;

The blocking state is returned to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server, wherein the target file The lock request is a file lock request whose file lock state is the polling blocking lock state.
The file lock processing method according to claim 1, wherein said obtaining the block chain list of the target file system comprises:

When receiving a file lock request from the target client for the target file in the target file system, obtain the block chain list of the target file system.
The file lock processing method according to claim 2, further comprising:

When the target file system supports asynchronous blocking locks, if the file lock request is a read request for the target file, the file lock state corresponding to the file lock request is determined to be the non-blocking lock state; if If the file lock request includes a write request to the target file, the file lock state corresponding to the file lock request is determined to be an asynchronous blocking lock state.
The file lock processing method according to claim 1, wherein said obtaining the block chain list of the target file system comprises:

Obtain the blocking chain list of the target file system every preset time interval.
The file lock processing method according to claim 2, wherein the determining the file lock status corresponding to each file lock request according to the request type of each file lock request comprises:

If the file lock request is a read request for the target file, determining the file lock state corresponding to the file lock request as the non-blocking lock state;

If the file lock request includes a write request for the target file, the file lock state corresponding to the file lock request is determined as the polling block lock state.
The file lock processing method according to claim 1, wherein the determining the file lock status corresponding to each file lock request according to the request type of each file lock request comprises:

Create a thread pool, and use the target thread in the thread pool to traverse the blocking chain list, so as to determine the file corresponding to each file lock request in the blocking chain table according to the request type of each file lock request Lock state.
A file lock processing device, which is characterized in that it is applied to a server and includes:

An obtaining module, configured to obtain a blocking chain list of the target file system; wherein the blocking chain table includes all file lock requests currently suspended by the target file system;

The judging module is used to judge whether the target file system supports asynchronous blocking lock; if not, start the work flow of the first determining module;

The first determining module is configured to determine the file lock state corresponding to each file lock request according to the request type of each file lock request; wherein, the file lock state includes a non-blocking lock state and a polling block Lock status

The return module is used to return the blocking state to the client that initiated the target file lock request, so that the client initiates the target file lock request every preset time until the target file lock request is responded by the server, wherein , The target file lock request is a file lock request whose file lock state is the polling block lock state.
7. The file lock processing device according to claim 7, wherein the acquiring module is specifically configured to acquire the blocking of the target file system when the target client receives a file lock request for the target file in the target file system. The module of the chain list.
An electronic device, characterized in that it comprises:

Memory, used to store computer programs;

The processor is configured to implement the steps of the file lock processing method according to any one of claims 1 to 6 when the computer program is executed.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the file lock processing method according to any one of claims 1 to 6 is realized A step of.