CN112650713A - File system operation method, device, equipment and storage medium - Google Patents
File system operation method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112650713A CN112650713A CN201910969421.8A CN201910969421A CN112650713A CN 112650713 A CN112650713 A CN 112650713A CN 201910969421 A CN201910969421 A CN 201910969421A CN 112650713 A CN112650713 A CN 112650713A
- Authority
- CN
- China
- Prior art keywords
- file
- operating system
- operation area
- processing flow
- call request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Abstract
The application provides an operation method, an operation device, equipment and a storage medium of a file system, wherein the method comprises the following steps: receiving a calling request of a source operating system; determining a corresponding file operation area according to the source operation system of the call request; determining the type of the call request and a processing flow corresponding to the type; and running the calling request based on the file operation area and the determined processing flow. According to the method, the isolated operation of the call request of the operating system is realized through the file operation area of the call request, and the stability and robustness of the operation of the file system are improved.
Description
Technical Field
The present application relates to computer software, and in particular, to a method, an apparatus, a device, and a storage medium for operating a file system.
Background
With the continuous abundance of functions of smart phones, mobile phones have played an indispensable role in daily life of people, and in order to meet the needs of people, mobile phones with dual-system architectures are rapidly developed, a kernel is shared by dual-android systems through a container technology, and the operation of the two android systems is supported through a lightweight virtualization technology. However, in the framework of the dual-android system, the same kernel is shared, file permissions of file systems of the two systems are failed due to conflict of application information in the kernel, and a traditional file system cannot smoothly run in the dual-android system, so that the performance of the file system is reduced.
Disclosure of Invention
The application provides an operation method, device, system and storage medium for a file system.
The embodiment of the application provides a method for operating a file system, which comprises the following steps: receiving a calling request of a source operating system; determining a corresponding file operation area according to the source operation system of the call request; determining the type of the call request and a processing flow corresponding to the type; and running the calling request based on the file operation area and the determined processing flow.
An embodiment of the present application provides an apparatus for operating a file system, including: the receiving module is used for receiving a calling request; the operation area determining module is used for determining a corresponding file operation area according to a source operation system of the calling request; the flow determining module is used for determining the type of the calling request and the processing flow corresponding to the type; and the request processing module is used for running the calling request based on the file operation area and the determined processing flow.
An embodiment of the present application provides an operating device of a file system, including: one or more processors; memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the method of any of the embodiments of the present application.
The embodiment of the application provides a storage medium, wherein a computer program is stored in the storage medium, and when being executed by a processor, the computer program realizes any one method in the embodiment of the application.
With regard to the above embodiments and other aspects of the present application and implementations thereof, further description is provided in the accompanying drawings description, detailed description and claims.
Drawings
Fig. 1 is a schematic diagram of a file system according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a method for operating a file system according to an embodiment of the present application;
fig. 3 is a flowchart of a method for operating a file system according to a second embodiment of the present application;
fig. 4 is an exemplary diagram of a method for operating a file system according to a second embodiment of the present application;
fig. 5a is a schematic structural diagram of an operating apparatus of a file system according to a third embodiment of the present application;
fig. 5b is an exemplary diagram of a running device of a file system according to a third embodiment of the present application;
fig. 6 is a schematic structural diagram of an operating device of a file system according to a fourth embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
In the prior art, more and more intelligent devices have functions of dual systems, a technology adopted by the dual systems is a container technology at present, the two systems share one kernel, for example, in a mobile phone with dual android systems, the two android systems are supported to run through a lightweight virtualization technology and are isolated in an operating system, fig. 1 is a schematic diagram of an architecture of a file system provided in an embodiment of the present application, see fig. 1, for example, the two operating systems may be a working operating system and a living operating system respectively, the two operating systems share an sdcardfs file system, and the working operating system and the living operating system completely and independently have the same mount directory processing flow and application information processing flow, and the like. Because two android systems share the same kernel system, the directory/config/sdcardfs of configfs is also shared, and both systems write the application information of the system into the directory. When the same apk is installed in two systems respectively, because the package names are the same, the two systems can write the appid into the same directory, and the later writing can cover the previously written data, so that the attribute confusion of the Android/data directory owner of the previous system is caused, and the problems that the system fails in accessing the directory by application are caused. For example, the two Android systems are a living system and a working system respectively, the living system is firstly provided with a public appraisal application, after the application is entered, the uid of the public appraisal application catalog com.dianping.vi is u0_ a170 and the uid of the public appraisal process is u0_ a170 under the Android/data catalog of the living system, and then the public appraisal application can be normally used. When the working system is switched to, the public commenting application is installed in the same way, the living system is switched back to check the directory condition, and the fact that the working system and the living system share the same set of kernel shows that the uid of the directory is disordered and becomes u0_ a5143, and the uid is the uid number used under the working system, so that the public commenting application of the living system cannot work normally. In order to realize that two operating systems share a kernel and use the same file system at the same time without influencing respective functions, the file system operation method is provided, and the isolated operation of the file system is realized.
Example one
Fig. 2 is a flowchart of a file system operation method provided in an embodiment of the present application, where this embodiment may be applicable to a case where a file system in a dual-system intelligent device operates, and the method may be executed by an operating apparatus of the file system, the apparatus may be integrated in an intelligent device, and the device may be implemented in a hardware and/or software manner, referring to fig. 2, where the method according to the embodiment of the present application includes:
The call request may be a request sent by an operating system to call a kernel of the file system, and may include, for example, modifying access rights of the application and updating mount directory information of the application, and the call request may be sent by the same operating system or different operating systems.
Specifically, the call requests sent by different operating systems may be accepted, one operating system may be used, or multiple operating systems may be used, for example, when an application is installed, a call request is sent by different operating systems, the call request generated when the application is installed may be received, and the call request may specifically include call requests such as creating a directory and calling a file.
And step 102, determining a corresponding file operation area according to the source operation system of the calling request.
The source operating system may be an operating system that issues a call request, for example, the intelligent device includes a work operating system and a living operating system, when the work operating system is in an installation application, the call request is issued, the work operating system may be used as the source operating system of the call request, the file operating region may be a region that stores kernel information of different operating systems, may be a physically isolated region, or may be a logically isolated region, for example, logical addresses of a mount directory of the work operating system and a mount directory of the living operating system in respective file operating regions may be the same, but actual physical addresses may be different, from the perspective of the kernel of the file system, the mount directories of different operating systems may have different keyword identifiers, such as a path of a directory of the work operating system, and data/media/0/Android/data from the perspective of the work operating system, in the view of the kernel of the file system, the absolute path corresponding to the working operating system is/data/cells/work/data/media/0/Android/data, so that the kernel of the file system can identify which operating system the mount directory belongs to by matching the keyword identification. The mount directory may store identification numbers of different operating systems, and the mount directory information including the respective identification numbers may be used as a file operation area corresponding to each operating system.
In the embodiment of the present application, different operating systems may correspond to different file operating regions, and the operating systems may all have corresponding file operating regions, the file operating area may belong to a file system, and may determine a source operating system of the call request, determine an operating system that issued the call request, for example, the device namespace of the call request may be parsed, information of the operating system that issued the call request may be obtained, the os corresponding to the os information may be used as the source os of the call request, specifically, the source os may have a corresponding relationship with the file operation area, the source os may have the same identification number or name as the file operation area, after the source operating system is obtained, the corresponding file operating area can be determined according to the source operating system.
And 103, determining the type of the call request and a processing flow corresponding to the type.
The types can be different types of called file system kernels, and can be divided into application information management, file system directory mounting, file system kernel object configuration and the like according to different types of called file system kernel information of the calling request; the processing flow may be a flow for processing the call request, and in this embodiment of the application, the processing flow may be a processing flow native to the file system, for example, the call request may be processed according to a native processing flow of sdcardfs, so as to update the mount directory mount and the kernel configuration file configfs.
Specifically, the type of the call request may be obtained by analyzing the call request, for example, the call request is a request for application information management, the type of the call request may be determined to be application information management, and after the type of the call request is determined, a corresponding call request processing flow may be obtained according to the type.
And step 104, running the calling request based on the file operation area and the determined processing flow.
In the embodiment of the present application, after determining the processing flow and the file operation area of the invocation request, the invocation request may be processed according to the obtained processing flow, and information generated in the processing process may be correspondingly stored in the file operation area, for example, when an application is installed or uninstalled, the corresponding processing request is obtained, the content of the sdcardfs _ system flag under the file system kernel file configfs may be modified, the operating system that issued the call request is the working operating system, obtaining the application information list of the corresponding area of the system according to the call request, updating the content of the application information list, adding or deleting the application information, the information of the mount directory mount of the working operating system can be obtained through traversal according to the call request, and updating the state of the mount directory according to the information of the mount directory mount, wherein the state can comprise the authority, the attribute and the like.
According to the technical scheme of the embodiment of the application, the source operating system of the call request is determined by receiving the call request, the corresponding file operating area is determined according to the source operating system, the processing flow is determined according to the type of the call request, the call request is operated according to the file operating area and the processing flow, the file system operation under the multi-operating system sharing the kernel is realized, the file operating areas of different operating systems are isolated, the conflict of file permissions is avoided, and the robustness and the usability of the file system are improved.
Example two
Fig. 3 is a flowchart of a method for operating a file system according to a second embodiment of the present application, where the embodiment of the present application is embodied based on the foregoing embodiment, and with reference to fig. 3, the method for operating a file system according to the embodiment of the present application includes:
Specifically, in the present application, the number of the operating systems may be multiple, each operating system may share one kernel, each operating system may send a call request for calling the kernel, and after the operating system sends the call request, the file system may receive the call request.
The device name space may be an identifier generated for identifying different operating systems when the operating systems generate the same type of call request, and since the call requests may be the same, the device name space may be written into the call request in order to distinguish the call requests, and the device name space may correspond to the operating systems.
In the embodiment of the application, the call request can be analyzed to obtain the device namespace, the obtained device namespace can be packaged as an interface, and when a source operating system of the call request needs to be obtained, the interface can be called to obtain the device namespace.
The identifier may be a unique identifier of the source operating system, the identifiers of different operating systems may be different, and the identifier may specifically be a character string composed of any suitable identifiers such as numbers, letters, and/or special characters.
Specifically, the device namespace may include an identifier of a source operating system of the call request, and the corresponding source operating system may be determined by the identifier of the standby request.
And 204, taking the file operation area corresponding to the identifier of the source operating system as the file operation area corresponding to the source operating system.
Specifically, the identifier of the source operating system and the file operating area may be managed and stored in advance, and after the large identifier of the source operating system is obtained, the corresponding file operating area may be searched according to the identifier, and the searched file operating area corresponding to the source operating system may be used. For example, the file operation area may include an identifier of the source operating system, and the file operation area corresponding to the source operating system may be used as the file operation area for processing the call request.
And step 205, when the type of the call request is application information management, determining that the processing flow corresponding to the type is an application information processing flow.
The application information management may be to perform operations such as creating a file or creating a directory according to application information of a corresponding operating system, and the processing flow may be a file system call flow native to a file system kernel, for example, a native system call flow of sdcardfs. The call request may be a call request for creating a directory, and the permission for creating the directory may be set according to application information in a system native flow, so that an application information list corresponding to an operating system initiated by the call request needs to be obtained, application information management may be implemented by operating the list, an application software number appid of an application corresponding to the directory may be queried, and the permission for creating the directory may be set according to the appid.
Specifically, if the call request is application information management, the native application information processing flow in the kernel of the file system may be acquired, a file or a directory may be created according to the application information of the corresponding operating system, for example, the authority and the attribute of the directory file may be updated, queried, deleted, or added according to the application information of the operating system corresponding to the call request.
And step 2051, searching a corresponding application information list in the file operation area.
The application information list may be a data table storing application information corresponding to the operating system, the application information list may be a hash list storing application information, and the application information list may correspond to different operating systems, for example, the native application information list is expanded, and a working system application hash list and a living system hash list are added. When the application information list needs to be operated, the corresponding application hash list can be obtained according to the source operating system. The native application information list can also be directly used, and the application information in the application information list is identified through the application package name and the system identification, so that the application information of different operating systems can be distinguished.
Specifically, the corresponding application information list may be searched in a file operation region corresponding to the call request, the corresponding application information list may be searched through an identifier of the source operating system, and the application information list may include a table name of the application information list and a correspondence of the operating system, or the application information list includes an identifier of the operating system.
And step 2052, processing the application information list according to the application information processing flow according to the calling request.
Specifically, after the application information list of the call request is determined, the application information list can be processed according to the original application information processing flow of the file system, so that the application information in the application information list can be added, deleted and/or updated.
And step 206, when the calling request type is the file system directory mounting, determining that the processing flow corresponding to the type is a mounting directory management flow.
The file system directory mount may refer to mapping a directory of a system to a specified directory by a certain file system type (e.g., sdcardfs type) mount (map), and the mount directory management process may be a native process for operating a mount directory in a file system, for example, an operating system initiates a file system directory mount request, and an operating system kernel performs operations such as binding a file directory, specifically, in Android, the system may query a directory/data/media mount to a/storage/organized directory by the sdcardfs type, at this time, the file operation area identifier may be recorded in the mount directory information in the present scheme, and in subsequent internal check object configuration operations, the directory mounted by the corresponding system may be queried by the identifier, and the statuses of the directories are updated.
In this embodiment of the present application, when the obtained call request is a file system directory mount request, a flow of operating a mount directory in a file system kernel may be determined, for example, when the file system is an sdcardfs file system, an operation of processing a mount directory may be determined as a mount directory management flow.
The mount directory may record an association relationship between file directories stored in the file system, the mount directory may be a mount directory corresponding to each operating system, and keywords of different operating systems may be in different mount directories, for example, the affiliation of the mount directory may be identified by an absolute path of the mount directory or node information of the mount directory, for example, a home or work included in the path may be used as a keyword for distinguishing the operating systems, and thus which system the mount directory belongs to may be identified, for example, the node information may trace back parent node information, and by recording root parent node information of a working or living system, which operating system the mount directory belongs to may be identified by comparing the root parent node information.
Specifically, the corresponding mount directory may be searched in the mount directory of the file operation area according to the identifier or the keyword of the operating system, and after the mount directory is determined, the identifier of the file operation area may be recorded in the mount directory.
Step 2062, processing the mount directory in the file operation area according to the mount directory management process according to the call request.
Specifically, after the mount directory is marked according to the operation identifier, processing can be performed according to the original mount directory operation, so as to realize the content of the call request.
And step 207, when the type of the calling request is the configuration of the kernel object of the file system, determining that the processing flow corresponding to the type is the kernel information processing flow.
The configuration of the kernel object of the file system may be a request for reconfiguring a kernel file of the file system, and the kernel information processing flow may include a flow for processing an application information list and a flow for processing a mount directory, and may specifically be a native processing operation of the file system.
Specifically, the type of the call request may be determined, and if the call request is configured for a kernel object of the file system, a flow for processing an application information list in the kernel of the file system and processing the mount directory may be determined.
Step 2071, obtaining an application information list corresponding to the file operation area, and updating the application information list according to the call request.
Specifically, the corresponding application information list may be searched for through the identifier of the operating system, and after the application information list is determined, the application information list is updated according to the call request, for example, the application information list may include addition, deletion, search, update, and the like of application information such as appid.
In the embodiment of the application, the mount directory information corresponding to the file operation area identifier is obtained, and the mount directories and the states of the files in the mount directories are updated according to the call request, wherein the states may include attributes, permissions and the like of the mount directories.
Fig. 4 is an exemplary diagram of a method for operating a file system according to a second embodiment of the present application, and referring to fig. 4, when an application in an operating system is installed or uninstalled, contents in a kernel file directory "/configfs/sdcardfs _ system flag" of the file system may be modified. The file operation area corresponding to the living system may be/configfs/sdcardfs _ home, and the file operation area corresponding to the working system may be/configfs/sdcardfs _ work. When detecting that the kernel sdcardfs monitors that the configfs file changes, determining that a call request is received, and reading application update information; the system identification of the invocation request may be obtained by the originating operating system. The corresponding application data list in the file operation area is obtained through the system identification, the application updating information is written into the application information list, then the mount information list can be traversed, the mount information list corresponding to the currently operated system identification is obtained, and the subsequent native processes, such as updating the directory attribute and the like, are performed on the directory contained in the obtained mount information list.
The technical scheme of the embodiment of the application comprises the steps of confirming a device name space of a call request by receiving the call request, obtaining an identifier of a source operating system according to the device name space, taking a file operating area corresponding to the identifier as a file operating area for processing the call request, if the request type of the call request is application information management, the processing flow is an application information processing flow, searching an application information list in the file operating area, processing the application information list according to the application information processing flow according to the call request, if the request type is file system directory mounting, the processing flow is a mounting directory management flow, recording the identifier of the file operating area into a mounting directory, processing the mounting directory according to the mounting directory management flow according to the call request, if the request type is correspondingly configured to a file system kernel, the processing flow is a kernel information processing flow, the application information list is updated according to the calling request, the corresponding mounting directory is updated according to the calling request, the operation of the file system is realized, the isolation of each operating system is realized, the conflict between the application information and the mounting directory authority when the same file system kernel is used is avoided, and the robustness and the usability of the file system under the multi-operating system are improved.
Further, on the basis of the foregoing embodiment, determining the corresponding file operating area according to the source operating system of the call request may further include:
reading a file storage path corresponding to the calling request; matching the file storage path with a preset operating system keyword by using a preset matching rule, and taking an operating system corresponding to the successfully matched preset operating system keyword as a source operating system of the call request; wherein the preset matching rule comprises at least one of the following: the file storage path comprises a preset operating system keyword or takes the preset operating system keyword as the beginning; and taking the file operation area corresponding to the source operating system identification as the file operation area for processing the call request.
The file storage path may be a storage path where the call request target file is located, for example, a storage path of a file system kernel file; the preset operating system keywords may be preset keywords for determining a source operating system, and may include work or life, and may also be characteristic path start/data/cells/work/xxxxx or/data/cells/home/xxxxx, for example; the matching rule may be a rule for matching the file storage path with a preset operating system keyword, and when the file storage path is matched with the preset system keyword through the matching rule, the operating system corresponding to the preset operating system keyword may be determined as a source operating system.
Specifically, the calling request may be analyzed to obtain a file storage path therein, if the file storage path includes a preset operating system keyword or starts with the preset operating system keyword, an operating system corresponding to the preset operating system keyword may be used as a source operating system that sends the calling request, and after the source operating system is determined, a file operating region that is stored in association with the source operating system may be a region where the calling request runs.
EXAMPLE III
Fig. 5a is a schematic structural diagram of an operating apparatus of a file system according to a third embodiment of the present application, which is capable of executing an operating method of a file system according to any embodiment of the present application, and has functional modules and beneficial effects corresponding to the executing method. The device can be implemented by software and/or hardware, and specifically comprises: a receiving module 401, an operation region determining module 402, a flow determining module 403, and a request processing module 404.
The receiving module 401 is configured to receive a call request of a source operating system.
An operation region determining module 402, configured to determine a corresponding file operation region according to the source operating system of the call request.
A flow determining module 403, configured to determine a type of the call request and a processing flow corresponding to the type.
A request processing module 404, configured to run the call request based on the file operation area and the determined processing flow.
According to the technical scheme of the embodiment of the application, the receiving module 401 receives the calling request, the operation area determining module 402 determines a source operating system of the calling request and determines a corresponding file operation area according to the source operating system, the flow determining module 403 determines a processing flow according to the type of the calling request, and the request processing module 404 runs the calling request according to the file operation area and the processing flow, so that file system running under a multi-operating system sharing a kernel is realized, file operation areas of different operating systems are isolated, file permission conflict is avoided, and robustness and usability of the file system are improved.
Further, on the basis of the foregoing application embodiment, fig. 5b is an exemplary diagram of an operating apparatus of a file system provided in the third application embodiment, and referring to fig. 5b, the flow determining module 403 may include:
the first determining unit 431 is configured to determine that a processing flow corresponding to the type is an application information processing flow when the type of the call request is application information management.
The second determining unit 432 is configured to determine, when the type of the call request is a file system directory mount, that a processing procedure corresponding to the type is a mount directory management procedure. The third determining unit 433 is configured to determine, when the type of the call request is a configuration of a kernel object of the file system, that a processing procedure corresponding to the type is a kernel information processing procedure.
Further, on the basis of the above embodiment of the present invention, the operation area determining module 402 includes:
the space confirmation unit 421 is configured to confirm the device namespace of the invocation request.
An identifier obtaining unit 422, configured to obtain an identifier of the source operating system according to the device namespace.
The first area determining unit 423 is configured to use the file operation area corresponding to the identifier of the source operating system as the file operation area corresponding to the source operating system.
Further, on the basis of the foregoing embodiment of the present invention, the operation region determining module 402 may further include:
and a path reading unit 424, configured to read a file storage path corresponding to the call request.
A matching unit 425, configured to match the file storage path with a preset operating system keyword by using a preset matching rule, and use an operating system corresponding to the successfully matched preset operating system keyword as a source operating system of the call request; wherein the preset matching rule comprises at least one of the following: the file storage path comprises a preset operating system keyword or takes the preset operating system keyword as the beginning;
a second area determining unit 426, configured to use the file operation area corresponding to the source operating system identifier as the file operation area for processing the call request.
Further, on the basis of the foregoing application embodiment, the request processing module 404 may specifically be configured to:
searching a corresponding application information list in the file operation area;
and processing the application information list according to the application information processing flow according to the calling request.
Further, on the basis of the foregoing application embodiment, the request processing module 404 may be further specifically configured to:
recording the identification of the file operation area to a mount directory in the file operation area;
and processing the mount directory in the file operation area according to the call request and the mount directory management process.
Further, on the basis of the above application embodiment, the request processing module 404 is further specifically configured to:
acquiring an application information list corresponding to a file operation area, and updating the application information list according to the calling request;
and acquiring the mounting directory with the file operation area identification, and updating the mounting directory according to the calling request.
Example four
Fig. 6 is a schematic structural diagram of an operating device of a file system according to a fourth embodiment of the present application, as shown in fig. 6, the device includes a processor 60, a memory 61, an input device 62, and an output device 63; the number of processors 60 in the device may be one or more, and one processor 60 is taken as an example in fig. 6; the processor 60, the memory 61, the input device 62 and the output device 63 in the apparatus may be connected by a bus or other means, as exemplified by the bus connection in fig. 6.
The memory 61 is a computer-readable storage medium that can be used to store software programs, computer-executable programs, and modules, such as program modules corresponding to the execution method of the file system in the embodiment of the present invention (for example, the receiving module 401, the operation region determining module 402, the flow determining module 403, and the request processing module 404 in the execution apparatus of the file system). The processor 60 executes various functional applications and data processing of the device by executing software programs, instructions and modules stored in the memory 61, that is, implements the above-described file system operation method.
The memory 61 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 61 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 61 may further include memory located remotely from the processor 60, which may be connected to the device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 62 may be used to receive entered numeric or character information and to generate key signal inputs relating to user settings and function controls of the apparatus. The output device 63 may include a display device such as a display screen.
It should be noted that the structure shown in fig. 6 is merely an illustration, and does not limit the structure of the above-described apparatus. For example, a device may also include more or fewer components than shown in FIG. 6, or have a different configuration than shown in FIG. 6.
EXAMPLE five
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a search method, the method including:
receiving a calling request of a source operating system;
determining a corresponding file operation area according to the source operation system of the call request;
determining the type of the call request and a processing flow corresponding to the type;
and running the calling request based on the file operation area and the determined processing flow.
Of course, the storage medium provided in the embodiments of the present application contains computer-executable instructions, and the computer-executable instructions are not limited to the method operations described above, and may also perform related operations in the search method provided in any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the operating apparatus of the file system, the included units and modules are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the application.
The above description is only exemplary embodiments of the present application, and is not intended to limit the scope of the present application.
It will be clear to a person skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a car mounted mobile station.
In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.
Any logic flow block diagrams in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), optical storage devices and systems (digital versatile disks, DVDs, or CD discs), etc. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.
The foregoing has provided by way of exemplary and non-limiting examples a detailed description of exemplary embodiments of the present application. Various modifications and adaptations to the foregoing embodiments may become apparent to those skilled in the relevant arts in view of the following drawings and the appended claims without departing from the scope of the invention. Therefore, the proper scope of the invention is to be determined according to the claims.
Claims (10)
1. An operating method of a file system, comprising:
receiving a calling request of a source operating system;
determining a corresponding file operation area according to the source operation system of the calling request;
determining the type of the call request and a processing flow corresponding to the type;
and running the calling request based on the file operation area and the determined processing flow.
2. The method of claim 1, wherein the determining the type of the call request and the processing flow corresponding to the type comprises:
when the calling request type is application information management, determining a processing flow corresponding to the type as an application information processing flow; or
When the calling request type is the file system directory mounting, determining that the processing flow corresponding to the type is a mounting directory management flow; or
And when the calling request type is configured for the kernel object of the file system, determining that the processing flow corresponding to the type is a kernel information processing flow.
3. The method of claim 1, wherein determining the corresponding file operating region according to the source operating system of the call request comprises:
confirming the device name space of the calling request;
acquiring the identifier of the source operating system according to the device namespace;
and taking the file operation area corresponding to the identifier of the source operating system as the file operation area corresponding to the source operating system.
4. The method of claim 1, wherein determining the corresponding file operating region according to the source operating system of the call request comprises:
reading a file storage path corresponding to the calling request;
matching the file storage path with a preset operating system keyword by using a preset matching rule, and taking an operating system corresponding to the successfully matched preset operating system keyword as a source operating system of the call request;
wherein the preset matching rule comprises at least one of the following:
the file storage path comprises a preset operating system keyword or takes the preset operating system keyword as the beginning;
and taking the file operation area corresponding to the source operating system identification as the file operation area for processing the call request.
5. The method according to claim 2, wherein when the processing flow is an application information processing flow, and accordingly, the executing the call request based on the file operation area and the determined processing flow includes:
searching a corresponding application information list in the file operation area;
and processing the application information list according to the application information processing flow according to the calling request.
6. The method according to claim 2, wherein when the system process flow is a mount directory management flow, and accordingly, the executing the call request based on the file operation area and the determined process flow includes:
recording the identification of the file operation area to a mount directory in the file operation area;
and processing the mount directory in the file operation area according to the call request and the mount directory management process.
7. The method according to claim 2, wherein when the system processing flow is a kernel information processing flow, and accordingly, the executing the call request based on the file operation area and the determined processing flow includes:
acquiring an application information list corresponding to a file operation area, and updating the application information list according to the calling request;
and acquiring the mounting directory with the file operation area identification, and updating the mounting directory according to the calling request.
8. An apparatus for operating a file system, comprising:
the receiving module is used for receiving a calling request of a source operating system;
the operation area determining module is used for determining a corresponding file operation area according to the source operation system of the calling request;
the flow determining module is used for determining the type of the calling request and the processing flow corresponding to the type;
and the request processing module is used for running the calling request based on the file operation area and the determined processing flow.
9. A file system execution apparatus, comprising:
one or more processors;
a memory for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910969421.8A CN112650713A (en) | 2019-10-12 | 2019-10-12 | File system operation method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910969421.8A CN112650713A (en) | 2019-10-12 | 2019-10-12 | File system operation method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112650713A true CN112650713A (en) | 2021-04-13 |
Family
ID=75343279
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910969421.8A Pending CN112650713A (en) | 2019-10-12 | 2019-10-12 | File system operation method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112650713A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407487A (en) * | 2021-06-07 | 2021-09-17 | 广东辰宜信息科技有限公司 | Data file management method, system and computer readable storage medium |
-
2019
- 2019-10-12 CN CN201910969421.8A patent/CN112650713A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407487A (en) * | 2021-06-07 | 2021-09-17 | 广东辰宜信息科技有限公司 | Data file management method, system and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7577686B1 (en) | Dynamic table configuration in a virtual machine | |
| US10725976B2 (en) | Fast recovery using self-describing replica files in a distributed storage system | |
| US8898167B2 (en) | Method of accessing files in electronic devices | |
| US8464242B2 (en) | Virtualization of configuration settings | |
| US20120011513A1 (en) | Implementing a versioned virtualized application runtime environment | |
| CN108268609B (en) | File path establishing and accessing method and device | |
| US20090164738A1 (en) | Process Based Cache-Write Through For Protected Storage In Embedded Devices | |
| US10650013B2 (en) | Access operation request management | |
| US11704114B2 (en) | Data structures for managing configuration versions of cloud-based applications | |
| US20210382711A1 (en) | Data structures for managing configuration versions of cloud-based applications | |
| CN112785248B (en) | Human resource data cross-organization interaction method, device, equipment and storage medium | |
| CN110659259A (en) | Database migration method, server and computer storage medium | |
| CN113296891A (en) | Multi-scene knowledge graph processing method and device based on platform | |
| US11416614B2 (en) | Statistical detection of firmware-level compromises | |
| US9971607B1 (en) | Method of accessing files in electronic devices | |
| CN112650713A (en) | File system operation method, device, equipment and storage medium | |
| CN112835638A (en) | Configuration information management method and device based on embedded application program | |
| CN113760306A (en) | Method and device for installing software, electronic equipment and storage medium | |
| US11200203B1 (en) | Accessing files stored in a firmware volume from a pre-boot application | |
| CN114116030A (en) | Operating system running method and device, electronic equipment and storage medium | |
| CN113111138A (en) | Data processing method, device, computing equipment and medium | |
| CN112100479A (en) | Application access method and device, electronic equipment and storage medium | |
| CN112749189A (en) | Data query method and device | |
| CN113312149B (en) | Password resetting method | |
| CN116701545A (en) | Audit data analysis method, audit data analysis device, storage medium and audit data processor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |