Method and system for configuring stable file system

Abstract

The invention provides a method and system for configuring a stable file system. A method is disclosed. The method includes receiving at least one input related to at least one file system configuration from a computing device via a user interface; saving, via at least one processor, one or more indicia corresponding to the at least one input into a factory reset protection module; initializing a boot phase of the computing device; reading the one or more flags from the factory reset protection module during a boot phase of the computing device; combining the one or more flags with a boot command line; transmitting the combined one or more flags to a kernel module of the computing device; using the kernel module to update one or more default parameters defined in the file system table file; and creating, using the kernel module, at least one file system configuration based at least on the file system table file.

Description

TECHNICAL FIELD

[0001] Example embodiments of the present disclosure relate generally to file systems in computing devices, and more particularly, to methods and systems for configuring a stable file system. BACKGROUND

[0002] Various industrial products and consumer devices use an operating system to perform one or more basic tasks. When a prior art error occurs, such industrial products and consumer devices often require a reboot. Typically, the operating system uses Universal Flash Storage (UFS) hardware and Flash Friendly File System (F2FS) to achieve higher performance rates. Additionally, the reboot of such operating systems involves the process of shutting down all running processes, closing active connections, and rebooting the core components of the system including the kernel and basic system services. Sometimes, a user initiates a reboot of the operating system by removing the battery from the industrial product and consumer device. Such a reboot action interrupts the power supply and effectively forces the operating system to abruptly shut down. As a result, upon reinserting the battery and rebooting the industrial product and consumer device, the operating system goes through a standard boot process. In such an event, the operating system often encounters file corruption caused by the problematic reboot.

[0003] The inventors have identified a number of areas for improvement in the prior art and processes, which are the subject of the embodiments described herein. Through the efforts, ingenuity, and innovation applied, many of these deficiencies, challenges, and problems have been addressed by developing solutions included in the embodiments of the present disclosure, some examples of which are described in detail herein. SUMMARY

[0004] The following presents a summary of some example embodiments to provide a basic understanding of some aspects of the present disclosure. This summary is not an extensive overview of the disclosure, and is not intended to identify key or critical elements of the present disclosure. It will be appreciated that the scope of the present disclosure encompasses many potential embodiments, including those not specifically outlined in this summary. The summary is provided to merely present some concepts of the present disclosure in a structure that is brief to the point.

[0005] In one example embodiment, a method is disclosed. The method includes receiving at least one input related to at least one file system configuration from a computing device via a user interface. Additionally, the method includes saving one or more flags corresponding to the at least one input to a factory reset protection module of the computing device via at least one processor. Furthermore, the method includes initializing a boot phase of the computing device via at least one processor. Additionally, the method includes reading the one or more flags from the factory reset protection module of the computing device during the boot phase of the computing device via at least one processor. Furthermore, the method includes combining the one or more flags with a boot command line via at least one processor. Furthermore, the method includes transmitting the one or more flags combined with the boot command line to a kernel module of the computing device via at least one processor. Additionally, the method includes updating one or more default parameters defined in a file system table file using the kernel module, at least based on the one or more flags, via at least one processor. Thereafter, the method includes creating the at least one file system configuration using the kernel module, at least based on a file system table file within the computing device, via at least one processor.

[0006] In some embodiments, the at least one input corresponds to enabling or disabling a barrier parameter. In some embodiments, when the barrier parameter is enabled, the at least one file system configuration enables slower but more stable file transfers within the memory of the computing device. In some embodiments, when the barrier parameter is disabled, the at least one file system configuration enables faster file transfers within the memory of the computing device.

[0007] In some embodiments, at least one processor is communicatively coupled to a bootloader. In some embodiments, the method includes using the bootloader via at least one processor during the boot phase of a computing device to read one or more flags stored in a factory reset protection module. In some embodiments, the method includes combining the one or more flags with a boot command line via at least one processor and using the bootloader to transmit the one or more flags to a kernel module.

[0008] In another example embodiment, a system is disclosed. The system includes a memory having one or more computer-readable instructions, and at least one processor communicatively coupled to the memory. The at least one processor, executing the one or more computer-readable instructions stored in the memory, is configured to receive at least one input related to at least one file system configuration from a computing device via a user interface. The at least one processor is also configured to save one or more flags corresponding to the at least one input to a factory reset protection module of the computing device. Furthermore, the at least one processor is configured to initialize a boot phase of the computing device. Additionally, the at least one processor is configured to read one or more flags from the factory reset protection module of the computing device. Furthermore, the at least one processor is configured to combine the one or more flags with a boot command line. Furthermore, the at least one processor is configured to transmit the one or more flags combined with the boot command line to a kernel module of the computing device. Additionally, the at least one processor is configured to update one or more default parameters defined in a file system table file using the kernel module, at least based on the one or more flags. Thereafter, the at least one processor is configured to create at least one file system configuration using the kernel module, at least based on a file system table file within the computing device.

[0009] In another example embodiment, a non-transitory machine-readable information storage medium is disclosed. The non-transitory machine-readable information storage medium includes one or more instructions that, when executed by at least one processor, perform operations including: receiving at least one input related to at least one file system configuration from a computing device; saving one or more flags corresponding to the at least one input to a factory reset protection module of the computing device; initializing a boot phase of the computing device; reading one or more flags from the factory reset protection module of the computing device during the boot phase of the computing device; combining the one or more flags with a boot command line; transmitting the one or more flags combined with the boot command line to a kernel module of the computing device; using the kernel module to update one or more default parameters defined in a file system table file, at least based on the one or more flags; and using the kernel module to create the at least one file system configuration, at least based on a file system table file within the computing device.

[0010] The foregoing overview is intended merely to outline some exemplary embodiments to provide a basic understanding of some aspects of this disclosure. Therefore, it will be understood that the above embodiments are merely illustrative and should not be construed as narrowing the scope or spirit of this disclosure in any way. It will be understood that, in addition to the embodiments outlined herein, the scope of this disclosure encompasses many potential embodiments, some of which will be further described below. Attached Figure Description

[0011] Having so generally described certain exemplary embodiments of this disclosure, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in the drawings:

[0012] Figure 1 The diagram illustrates a block diagram of a system with a configured stable file system according to an example embodiment of the present disclosure;

[0013] Figure 2 The illustration shows a block diagram of a method for configuring a stable file system according to an example embodiment of the present disclosure;

[0014] Figure 3 The illustration shows a configuration page of a user interface installed in a computing device according to an example embodiment of the present disclosure; and

[0015] Figure 4 The illustration shows a flowchart of a method for configuring a stable file system according to an example embodiment of the present disclosure. Detailed Implementation

[0016] Some embodiments will now be described more fully below with reference to the accompanying drawings, in which some, but not all, embodiments of the present disclosure are shown. In fact, various embodiments may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present disclosure will satisfy applicable legal requirements.

[0017] The components illustrated in the figures represent components that may or may not be present in the various embodiments of this disclosure described herein, such that embodiments may include fewer or more components than those shown in the figures without departing from the scope of this disclosure. For visibility of lower-level components, some components may be omitted from one or more figures or shown with dashed lines.

[0018] As used herein, the term “comprising” means including but not limited to, and should be interpreted in the manner commonly used in the patent context. The use of broader terms such as including, comprising, and having should be understood as support for narrower terms such as consisting of, substantially consisting of, and substantially constituted by.

[0019] The phrases “in various embodiments,” “in one embodiment,” “according to one embodiment,” “in some embodiments,” and the like generally mean that the specific feature, structure, or characteristic following the phrase may be included in at least one embodiment of this disclosure, and may be included in more than one embodiment of this disclosure (importantly, such phrases do not necessarily refer to the same embodiment).

[0020] The terms “example” or “exemplary” as used herein mean “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations.

[0021] If the specification states that a component or feature is "may," "can," "may," "should," "will," "preferably," "possibly," "typically," "optionally," "for example," "often," or "maybe" (or other such language) included or has that characteristic, then it is not required that a particular component or feature be included or have that characteristic. Such a component or feature may be optionally included in some embodiments, or it may be excluded.

[0022] This disclosure provides various embodiments of methods and systems for configuring a stable file system. Embodiments may include a memory having one or more computer-readable instructions. Embodiments may include at least one processor communicatively coupled to the memory. Embodiments may be configured to receive at least one input related to at least one file system configuration from a computing device via a user interface. Embodiments may save one or more flags corresponding to at least one input to a factory reset protection module of the computing device. Embodiments may be configured to initialize the boot phase of the computing device. Embodiments may be configured to read one or more flags from the factory reset protection module of the computing device. Embodiments may be configured to combine one or more flags with a boot command line. Embodiments may be configured to transmit one or more flags combined with the boot command line to a kernel module of the computing device. Embodiments may be configured to use the kernel module to update one or more default parameters defined in a file system table file, at least based on the one or more flags. Embodiments may be configured to use the kernel module to create at least one file system configuration, at least based on a file system table file within the computing device.

[0023] Figure 1 A block diagram of a system 100 with a configured stable file system according to an example embodiment of the present disclosure is illustrated. System 100 includes a computing device 102. The computing device 102 may include a user interface 104, at least one processor 106 communicatively coupled to a memory 108, at least one file system configuration 110, input / output circuitry 112, and communication circuitry 114. Additionally, system 100 may include one or more user devices 118 communicatively coupled to the computing device 102 via a network 116.

[0024] In some embodiments, system 100 may correspond to a stable file system. In some embodiments, system 100 may include computing device 102. In some embodiments, computing device 102 may include, but is not limited to, mobile phones, tablets, etc. In some embodiments, a user may access computing device 102 to perform one or more operations. Additionally, one or more operations may include providing a medium for input data / information, communicating with one or more other external devices, displaying images, and providing at least one of various outputs.

[0025] In some embodiments, computing device 102 further includes a user interface 104. Additionally, user interface 104 may be configured to allow a user to provide at least one input. In some embodiments, the at least one input may correspond to one or more parameters provided via user interface 104 in relation to at least one file system configuration 110. In some embodiments, the one or more parameters include barrier parameters. Additionally, barrier parameters may correspond to one or more license sets associated with memory 108 of computing device 102. Furthermore, user interface 104 may correspond to at least one of a graphical user interface (GUI), a command-line interface (CLI), and an application programming interface (API). In at least one example, user interface 104 may include a home page, one or more redirected pages, and one or more tabs linked to the home page. In some embodiments, user interface 104 may be operatively coupled to at least one processor 106.

[0026] In some embodiments, at least one processor 106 may include suitable logic, circuitry, and / or interfaces operable to execute one or more instructions stored in memory 108 to perform a predetermined operation. In one embodiment, at least one processor 106 may be configured to decode and execute any instructions received from one or more other electronic devices or servers. At least one processor 106 may be configured to execute one or more computer-readable program instructions, such as program instructions that perform any of the functions described herein. Additionally, at least one processor 106 may be implemented using one or more processor technologies known in the art. Examples of at least one processor 106 include, but are not limited to, one or more general-purpose processors and / or one or more special-purpose processors.

[0027] In some embodiments, at least one processor 106 may be configured as a central processing unit (CPU) of the computing device 102. In some embodiments, at least one processor 106 may be configured to execute instructions and manage computing tasks associated with the computing device 102. In some embodiments, the computing device 102 may further include an operating system. In some embodiments, the operating system may be installed within the computing device 102 and may be operated by a user. In some embodiments, memory 108 may be configured to store one or more instruction sets associated with the operating system.

[0028] In some embodiments, the operating system and memory 108 may be configured to execute one or more instruction sets that enable at least one processor 106 to perform one or more operations. In some embodiments, the one or more operations may include at least one of data acquisition, data filtering, data processing, etc. In some embodiments, the operating system may include multiple modules. Additionally, the multiple modules may include a framework, a factory reset protection module, a bootloader, and a kernel module.

[0029] In some embodiments, at least one processor 106 may be configured to communicate with an operating system using multiple hardware interfaces and software protocols. Additionally, the multiple hardware interfaces may include one or more buses and ports. Furthermore, the multiple hardware interfaces may be configured to enable the transmission and exchange of signals and data through / from at least one processor 106. In some embodiments, the operating system may be configured to serve as a software platform. Additionally, the operating system may be configured to manage one or more resources associated with the computing device 102. In some embodiments, the operating system may be configured to provide an environment for running one or more applications on the computing device 102.

[0030] In some embodiments, the operating system may further include a system interface. In some embodiments, the system interface may be configured to display information associated with one or more operations performed by at least one processor 106. Additionally, the system interface may be configured to allow a user to add, update, delete, or replace one or more system configurations. In some embodiments, the framework may be configured to enable the operating system to communicate with memory 108 via at least one processor 106. In some embodiments, a bootloader may be configured to initialize the operating system on the computing device 102. Additionally, the bootloader may correspond to a first software program configured to execute, perform hardware initialization, and check the integrity of the computing device 102.

[0031] In some embodiments, the operating system and memory 108 may be configured to enable at least one processor 106 to receive at least one input provided by a user through user interface 104. Additionally, the at least one input may be associated with at least one file system configuration 110. Furthermore, the at least one processor 106 may be configured to save one or more flags to a factory reset protection module of the computing device 102. Additionally, the one or more flags may be associated with at least one input provided by a user through user interface 104 of the computing device 102. Furthermore, the one or more flags may correspond to read flags, write flags, hold flags, and transfer flags.

[0032] In at least one example, at least one input may correspond to enabling the barrier parameter. In various other examples, at least one input may correspond to disabling the barrier parameter. Additionally, the barrier parameter may include one or more permission sets associated with one or more flags. In some embodiments, the one or more permission sets may be configured to enable or block the operation of one or more flags. Furthermore, when the barrier parameter is enabled, at least one file system configuration 110 may enable slower but more stable file transfers within the memory 108 of the computing device 102. Conversely, when the barrier parameter is disabled, at least one file system configuration 110 enables faster file transfers within the memory 108 of the computing device 102.

[0033] In some embodiments, computing device 102 may include memory 108. Additionally, memory 108 may be communicatively coupled to at least one processor 106. In some embodiments, memory 108 may be configured to store a set of instructions and data executable by at least one processor 106. Furthermore, memory 108 may include one or more instructions executable by at least one processor 106 and an operating system to perform a specific operation. It will be apparent to those skilled in the art that one or more instructions stored in memory 108 enable the hardware of computing device 102 to perform a predetermined operation. Some known memory implementations include, but are not limited to, random access memory (RAM) and read-only memory (ROM). In some embodiments, memory 108 may further include data partitioning, metadata partitioning, and a factory reset protection module.

[0034] In some embodiments, at least one processor 106 may be configured to save one or more flags corresponding to at least one input to a factory reset protection module provided in memory 108. In some embodiments, at least one processor 106 may be configured to save one or more flags to the factory reset protection module via a frame. In some embodiments, the frame may include a factory reset protection manager. In some embodiments, the factory reset protection manager may be configured to save one or more flags to the factory reset protection module. Additionally, the factory reset protection manager may be configured to control and monitor the data management of the factory reset protection module.

[0035] In at least one example, after successfully saving one or more flags to the factory reset protection module, at least one processor 106 may be configured to prompt a user to manually restart the computing device 102 by pressing and holding at least one power button provided to the computing device 102. Additionally, at least one processor 106 may be configured to instruct the user interface 104 to display at least one pop-up notification. Furthermore, at least one pop-up notification may be configured to instruct the user to restart the computing device 102 using at least one power button. In some embodiments, after the computing device 102 successfully restarts, at least one processor 106 initializes the boot phase of the computing device 102.

[0036] In another example, after successfully saving one or more flags to the factory reset protection module, at least one processor 106 can be configured to prompt the user to restart the computing device 102 by displaying at least one virtual button. Additionally, the at least one virtual button can be designed such that pressing the at least one virtual button on the user interface 104 initiates a restart of the computing device 102 by the operating system. Furthermore, at least one processor 106 can be configured to instruct the user interface 104 to display at least one pop-up notification. Additionally, at least one pop-up notification can be configured to instruct the user to restart the system 100 using at least one virtual button. In some embodiments, after the computing device 102 successfully restarts, at least one processor 106 initializes the boot phase of the computing device 102. Furthermore, the boot phase can correspond to the initialization of one or more resources associated with the computing device 102. In at least one example, the boot phase can correspond to a time period (i.e., 5-20 seconds).

[0037] In various other examples, after successfully saving one or more flags to the factory reset protection module, the operating system of computing device 102 can cause at least one processor 106 to initiate a restart of computing device 102. In some embodiments, the operating system may include one or more instructions that can cause at least one processor 106 to restart computing device 102. Additionally, one or more instructions may be stored in memory 108. Furthermore, at least one processor 106 may be configured to instruct user interface 104 to display at least one pop-up notification. Additionally, at least one pop-up notification may be configured to warn the user about the initialization of the restart of computing device 102. In some embodiments, after computing device 102 successfully restarts, at least one processor 106 initiates the boot phase of computing device 102.

[0038] In some embodiments, at least one processor 106 may be configured to read one or more flags from the factory reset protection module using a bootloader. Additionally, during the boot phase of the computing device 102, the bootloader may cause at least one processor 106 to read one or more flags from the factory reset protection module.

[0039] In some embodiments, at least one processor 106 may be configured to combine one or more flags with a boot command line of the operating system. In some embodiments, the one or more flags may include one or more read flags of a factory reset protection module. In some embodiments, the boot command line may correspond to an interface that can be configured to interact with the operating system. Additionally, at least one processor 106 may be configured to transmit one or more flags combined with the boot command line to a kernel module of the computing device 102. In some embodiments, the kernel module may be configured to manage one or more services associated with the operating system. Additionally, the one or more services may include at least one of process management, memory management, device drivers, and security mechanisms. In some embodiments, the boot command line may be used to navigate the file system, manipulate files and directories within memory 108, install or uninstall applications, and view system logs. Additionally, at least one processor 106 may be configured to read one or more flags from the boot command line of the operating system. Furthermore, at least one processor 106 utilizes the kernel module of the operating system to read one or more flags from the boot command line.

[0040] In some embodiments, at least one processor 106 may be configured to update one or more default parameters defined in a file system table file based on at least one or more flags. Additionally, a kernel module may be configured to cause at least one processor 106 to update one or more parameters defined in the file system table file of the operating system. In some embodiments, the file system table file may be configured to ensure that at least one file system configuration 110 is configured within the computing device 102. In at least one example, when one or more default parameters can be updated by at least one processor 106, at least one file system configuration 110 enables slower but more stable file transfers within the memory 108 of the computing device 102. In another example, when one or more default parameters remain unchanged, at least one file system configuration 110 enables faster file transfers within the memory 108 of the computing device 102.

[0041] In some embodiments, at least one processor 106 may be configured to create at least one file system configuration 110 using a kernel module based at least on a file system table file within the computing device 102. In some embodiments, when a barrier parameter can be enabled, at least one processor 106 having a kernel module may be configured to update one or more license sets associated with data partitions and metadata partitions.

[0042] In some embodiments, computing device 102 may further include input / output circuitry 112. Input / output circuitry 112 enables a user to communicate or interact with one or more user devices 118 via computing device 102. One or more user devices 118 may include N number of user devices. In some embodiments, input / output circuitry 112 may act as a medium for transmitting input from and from an interface to computing device 102. In some embodiments, input / output circuitry 112 may refer to hardware and software components that facilitate information exchange between computing device 102 and one or more user devices 118. In at least one example, computing device 102 may include a user interface 104 as input circuitry to allow one or more users to input data. Input / output circuitry 112 may include various input devices for providing data to one or more users, such as a keyboard, barcode scanner, or GUI, and various output devices for receiving data from one or more users, such as a display or printer. In another example, input / output circuitry 112 may include various output circuitry, such as a display showing alarms and / or readings associated with one or more media.

[0043] In some embodiments, computing device 102 may further include communication circuitry 114. Communication circuitry 114 may allow at least one processor 106 to exchange data or information with other systems or devices. Additionally, communication circuitry 114 may include network interfaces, protocols, and software modules responsible for sending and receiving data or information. In some embodiments, communication circuitry 114 may include an Ethernet port, a Wi-Fi adapter, or a communication protocol such as HTTP or MQTT for connecting to other systems. Communication circuitry 114 may further include components such as communication modules (e.g., Wi-Fi, Ethernet, cellular), transceivers, antennas, and protocols for exchanging data with other systems or network devices (e.g., TCP / IP, MQTT, SNMP). Communication circuitry 114 may allow at least one processor 106 to stay up-to-date and accurately track at least one standardized alarm.

[0044] In some embodiments, the input / output circuit 112 and the communication circuit 114 may be configured to integrate at least one standardized alarm data with other systems, such as Supervisory Control and Data Acquisition (SCADA), Building Management System (BMS), Enterprise Asset Management (EAM) system, or third-party monitoring platform, for centralized monitoring, analysis, and control of operators and automated processes.

[0045] In some embodiments, input / output circuitry 112 and communication circuitry 114 may be configured to enable computing device 102 to communicate with one or more user devices 118. In one example, computing device 102 may be configured to operate as a centralized server that can establish a network 116 with each of the one or more user devices 118. Additionally, at least one processor 106 may be configured to create at least one file system configuration 110 in each of the one or more user devices 118.

[0046] It will be apparent to those skilled in the art that the aforementioned components of system 100 have been provided for illustrative purposes only and without departing from the scope of this disclosure.

[0047] Figure 2 A block diagram 200 illustrates a method for configuring a stable file system according to an example embodiment of the present disclosure.

[0048] First, a user can access user interface 104 to provide at least one input to computing device 102. In some embodiments, the at least one input may be associated with one or more flags in memory 108. In some embodiments, the at least one input may correspond to enabling or disabling a barrier parameter. Additionally, one or more flags may be associated with at least one input provided by the user through user interface 104 of computing device 102. Furthermore, one or more flags may correspond to read flags, write flags, hold flags, and transfer flags.

[0049] In some embodiments, a read flag may be configured to define operations of at least one processor 106 associated with accessing data within memory 108. In some embodiments, the read flag may correspond to a license set that enables or prevents at least one processor 106 from accessing data within memory 108. Additionally, a write flag may be configured to define operations of at least one processor 106 associated with inserting, updating, and deleting data. Furthermore, a hold flag may be configured to prevent at least one processor 108 from accessing memory 108. Additionally, a transfer flag may be configured to define operations of at least one processor 106 associated with transferring data to other external resources of computing device 102.

[0050] Subsequently, at least one processor 106 can be configured to read one or more flags associated with at least one input provided by user interface 104. Additionally, frame 202, together with memory 108, enables at least one processor 106 to read one or more flags. In some embodiments, frame 202 may employ factory reset protection module manager 204 to read one or more flags provided by user interface 104. Furthermore, factory reset protection module manager 204 can be configured to control and monitor data management of memory 108.

[0051] Subsequently, at least one processor 106 may be configured to save one or more flags corresponding to at least one input to the factory reset protection module 206. Additionally, the factory reset protection module 206 may be provided within memory 108. In some embodiments, at least one processor 106 may be configured to save one or more flags to a factory reset protection partition via frame 202. In some embodiments, frame 202 may include a factory reset protection module manager 204. In some embodiments, the factory reset protection module manager 204 may be configured to save one or more flags to the factory reset protection module 206.

[0052] Subsequently, at least one processor 106 may be configured to read one or more flags from the factory reset protection module 206 of the memory 108. In some embodiments, at least one processor 106 may be configured to read one or more flags from the factory reset protection module 206 during the boot phase of the computing device 102. In some embodiments, at least one processor 106 may employ a bootloader 208 to read one or more flags from the factory reset protection module 206. Additionally, the boot phase may correspond to the initialization of one or more resources associated with the system 100. Furthermore, the boot phase may correspond to the initialization of one or more resources associated with the computing device 102. In at least one example, the boot phase may correspond to a time period (i.e., 5-20 seconds).

[0053] Subsequently, at least one processor 106 can be configured to combine one or more flags with the operating system's boot command line. Additionally, at least one processor 106 can utilize bootloader 208 to combine one or more flags with the boot command line. In some embodiments, the boot command line may correspond to an interface that can be configured to interact with the operating system. In some embodiments, the boot command line can be used to navigate the file system, manipulate files and directories within memory 108, install or uninstall applications, and view system logs. In some embodiments, the boot command line can be used to navigate at least one file system configuration 110, manipulate files and directories within memory 108, install or uninstall applications, and view system logs. Additionally, at least one processor 106 can be configured to read one or more flags from the operating system's boot command line. Furthermore, at least one processor 106 utilizes the operating system's kernel module 210 to read one or more flags from the boot command line.

[0054] Subsequently, at least one processor 106 may be configured to pass one or more flags combined with the boot command line to kernel module 210. In at least one example, at least one processor 106 may be configured to pass one or more flags combined with the boot command line to kernel module 210 of the operating system. In various other examples, at least one processor 106 may be configured to resolve the combined one or more flags to kernel module 210 of the operating system. In some embodiments, kernel module 210 may be configured to manage one or more services associated with the operating system. Additionally, the one or more services may include at least one of process management, memory management, device drivers, and security mechanisms.

[0055] Subsequently, at least one processor 106 may be configured to update one or more default parameters defined in a filesystem table file based at least on one or more flags. In some embodiments, at least one processor 106 may be configured to use kernel module 210 to update one or more parameters to the operating system's default filesystem table file based at least on at least one input provided through user interface 104. In some embodiments, the default filesystem table file may be configured to ensure the configuration of a faster filesystem or a stable filesystem. In at least one example, the default filesystem table file remains unchanged when one or more parameters can be associated with a faster filesystem. In various other examples, when one or more parameters can be associated with a stable filesystem, at least one processor 106 may be configured to update the default filesystem table file using one or more parameters provided by the user through user interface 104.

[0056] Subsequently, at least one processor 106 can be configured to load one or more updated default parameters into the factory reset protection module 206. Additionally, the operating system, along with memory 108, can enable at least one processor 106 to update one or more flags. Furthermore, the updated one or more flags can be configured to update the permissions of at least one processor 106 associated with accessing, editing, or transferring data.

[0057] Figure 3 The illustration shows a configuration page of a user interface 104 installed in a computing device 102 according to an example embodiment of the present disclosure.

[0058] In some embodiments, the user interface 104 may include a configuration page. Additionally, the configuration page may be configured to provide a software platform to the user for mounting at least one file system configuration 110 within the computing device 102. Furthermore, the configuration page may include one or more lists. Additionally, the one or more lists may include at least one of DEVICE CONFIG. Additionally, DEVICE CONFIG may include one or more sub-lists (HHP RESERVED, WIRELESS ANDNETWORKS, DEVICE, DEVICE, PERSONAL, and SYSTEM). Additionally, SYSTEM further includes one or more virtual buttons. Additionally, the one or more virtual buttons may include at least one of FASTER FILESYSTEM, HIDEEMERGENCYBUTTON, ENABLEDOWNGRADEWITHENTERPRISE_R, DISABLE ANDROIDSETTINGS APP, and DISABLE APPLICATION STATE. In some embodiments, the configuration page further includes one or more input fields (KEY, VALUE, and DESC).

[0059] In some embodiments, system 100 may include computing device 102. Additionally, computing device 102 may include at least one of a mobile phone, tablet computer, etc. Furthermore, computing device 102 may be configured to enable a user to perform one or more operations. These one or more operations may include, but are not limited to, communicating with other external systems or devices, performing computation-oriented tasks, and providing auditory-visual output. In one example, computing device 102 may include a touch-enabled display panel, one or more speakers, one or more microphones, one or more antennas, etc. Additionally, the touch-enabled display panel may be configured to provide multiple visual outputs. Additionally, one or more speakers may be configured to provide audio output. Additionally, one or more microphones may be configured to record audio input provided by the user.

[0060] In some embodiments, computing device 102 may be equipped with user interface 104. Additionally, user interface 104 may be configured to provide a software platform for communicating with computing device 102 or other external devices using computing device 102. In some embodiments, user interface 104 may include one or more navigation bars, input fields, virtual buttons, and various other interactive elements. In some embodiments, a user can access user interface 104 to interact with computing device 102. In some embodiments, user interface 104 may be communicatively coupled to at least one processor 106. Furthermore, user interface 104 may be configured to enable a user to use virtual buttons to provide at least one input related to at least one file system configuration 110.

[0061] Figure 4 The illustration shows a flowchart of a method 400 for configuring a stable file system according to another example embodiment of the present disclosure.

[0062] At operation 402, user interface 104 can be configured to receive at least one input from computing device 102 related to at least one file system configuration 110. In some embodiments, the at least one input may correspond to one or more parameters associated with at least one file system configuration 110. Additionally, the at least one input corresponds to enabling or disabling a barrier parameter. Furthermore, based on at least one input, a file transfer rate can be defined within memory 108 of computing device 102.

[0063] For example, the mobile phone is equipped with a user interface 104. Additionally, the mobile phone includes a memory 108 having at least one file system configuration 110. Furthermore, the user interface 104 is accessed by a user to provide at least one input associated with the at least one file system configuration 110. The at least one input may correspond to one or more parameters associated with the at least one file system configuration 110. Additionally, the at least one input corresponds to a barrier parameter within the memory 108 that enables the mobile phone. Furthermore, the at least one file system configuration 110 is associated with faster file transfer within the memory 108.

[0064] At operation 404, at least one processor 106 may be configured to save one or more flags corresponding to at least one input to the factory reset protection module 206 of the computing device 102. Additionally, the factory reset protection module 206 may be provided within memory 108. Furthermore, the one or more flags may include one or more read flags and one or more write flags. In some embodiments, at least one processor 106 may be configured to save one or more flags to a factory reset protection partition via frame 202. In some embodiments, frame 202 may include a factory reset protection module manager 204. In some embodiments, the factory reset protection module manager 204 may be configured to save one or more flags to the factory reset protection module 206.

[0065] For example, the mobile phone includes at least one processor 106 and a memory 108. Additionally, the at least one processor 106 is configured to save at least one input to a factory reset protection module 206 within the memory 108. Furthermore, the mobile phone includes a frame 202 having a factory reset protection module manager 204. Additionally, the factory reset protection module manager 204 can be configured to save one or more flags to the factory reset protection module 206 within the memory 108.

[0066] At operation 406, at least one processor 106 can be configured to initialize the boot phase of the computing device 102. Furthermore, the boot phase can correspond to the initialization of one or more resources associated with the computing device 102. Additionally, the boot phase can correspond to a time period (i.e., 5-20 seconds).

[0067] For example, the mobile phone includes a display panel and buttons. Additionally, after saving one or more flags to the factory reset protection module 206 in memory 108, the display panel is configured to display a notification to instruct the user to restart the mobile phone. Furthermore, the user presses a button for a predetermined period of time to initiate a restart of the mobile phone. Additionally, at least one processor 106 is configured to initiate a boot phase for the mobile phone.

[0068] At operation 408, at least one processor 106 may be configured to read one or more flags from the factory reset protection module 206 of the computing device 102 during the boot phase of the computing device 102. Additionally, at least one processor 106 may be communicatively coupled to the bootloader 208. Furthermore, at least one processor 106 may be configured to read one or more flags from the factory reset protection module 206 using the bootloader 208.

[0069] For example, at least one processor 106 is configured to read one or more flags from the factory reset protection module 206 of the memory 108 within the mobile phone during the boot phase. Additionally, the mobile phone includes a bootloader 208. Furthermore, the bootloader 208 can cause at least one processor 106 to read one or more flags from the factory reset protection module 206 during the boot phase.

[0070] At operation 410, at least one processor 106 is configured to combine one or more flags with a boot command line. Additionally, bootloader 208 may cause at least one processor 106 to combine one or more flags with a boot command line. In some embodiments, the one or more flags may include one or more read flags of the factory reset protection module 206. In some embodiments, the boot command line may correspond to an interface that can be configured to interact with the operating system of computing device 102.

[0071] For example, the mobile phone includes an operating system. Additionally, at least one processor 106 is configured to combine one or more flags with the operating system's boot command line. Furthermore, a bootloader 208 is configured to cause at least one processor 106 to combine one or more flags with the boot command line.

[0072] At operation 412, at least one processor 106 may be configured to transmit one or more flags combined with a boot command line to the kernel module 210 of the computing device 102. Additionally, at least one processor 106 may be configured to transmit one or more flags combined with a boot command line to the kernel module 210 of the computing device 102. In some embodiments, the kernel module 210 may be configured to manage one or more services associated with the operating system. Furthermore, the one or more services may include at least one of process management, memory management, device drivers, and security mechanisms.

[0073] For example, the operating system of a mobile phone includes a kernel module 210. Additionally, at least one processor 106 of the mobile phone is configured to transmit one or more flags, combined with a boot command line, to the kernel module 210 of the computing device 102.

[0074] At operation 414, at least one processor 106 may be configured to use kernel module 210 to update one or more default parameters defined in a filesystem table file, based at least on one or more flags. In some embodiments, at least one processor 106 may be configured to use kernel module 210 to update one or more parameters to the operating system's default filesystem table file. In some embodiments, the default filesystem table file may be configured to ensure that at least one filesystem configuration 110 has a configuration that allows for slower but more stable file transfers within memory 108, or faster file transfers within memory 108.

[0075] For example, at least one processor 106 is configured to use kernel module 210 to update one of the default parameters defined in a filesystem table file, based on at least one or more flags. Additionally, the updated one or more parameters correspond to barrier parameters. Furthermore, based on the updated one or more parameters within the filesystem table file, at least one filesystem configuration 110 is defined, exhibiting a faster file transfer rate within memory 108.

[0076] At operation 416, at least one processor 106 may be configured to create at least one file system configuration 110 using kernel module 210, based at least on file system table files within computing device 102. In some embodiments, when barrier parameters can be enabled, at least one processor 106 having kernel module 210 may be configured to update one or more license sets associated with data partitions and metadata partitions of memory 108.

[0077] For example, at least one processor 106 is configured to create at least one file system configuration 110 with a faster file transfer rate within memory 108. Additionally, kernel module 210 enables at least one processor 106 to update one or more license sets associated with the data partition and metadata partition of memory 108, based at least on enabled barrier parameters.

[0078] In some embodiments, system 100 may include at least one non-transitory machine-readable medium containing data that, when used by at least one processor 106, causes at least one processor 106 to execute instructions that cause at least one processor 106 to perform operations, including receiving at least one input from computing device 102 related to at least one file system configuration 110. The at least one input may correspond to enabling or disabling barrier parameters. When barrier parameters are enabled, at least one file system configuration 110 may enable slower but more stable file transfers within memory 108 of computing device 102. When barrier parameters are disabled, at least one file system configuration 110 may enable faster but less stable file transfers within memory 108 of computing device 102.

[0079] Additionally, the operation includes saving one or more flags corresponding to at least one input to the factory reset protection module 206 of the computing device 102. Additionally, the operation includes initializing the boot phase of the computing device 102. Additionally, the operation includes reading one or more flags from the factory reset protection module 206 of the computing device 102. Additionally, the operation includes combining one or more flags with a boot command line. Additionally, the operation includes transmitting one or more flags combined with the boot command line to the kernel module 210 of the computing device 102. Additionally, the operation includes using the kernel module 210 to update one or more default parameters defined in a filesystem table file, based at least on one or more flags. Additionally, the operation includes using the kernel module 210 to create at least one filesystem configuration 110, based at least on a filesystem table file within the computing device 102.

[0080] Benefiting from the teachings presented in the foregoing description and associated drawings, those skilled in the art to which this disclosure pertains will conceive of many modifications and other embodiments of the disclosure set forth herein. Therefore, it is to be understood that this disclosure is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary embodiments in contexts of certain example combinations of elements and / or functions, it should be appreciated that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above, as set forth in some of the appended claims, are also contemplated. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

Claims

1. A method comprising: Receive at least one input related to at least one file system configuration from the computing device via a user interface; One or more flags corresponding to the at least one input are saved to the factory reset protection module of the computing device via at least one processor; The boot phase of the computing device is initialized via the at least one processor; The one or more flags are read from the factory reset protection module of the computing device during the boot phase of the computing device via the at least one processor; The one or more flags are combined with the boot command line via the at least one processor; One or more flags combined with the boot command line are transmitted to the kernel module of the computing device via the at least one processor; The kernel module updates one or more default parameters defined in the file system table file, at least based on one or more flags, via the at least one processor. as well as The at least one file system configuration is created using a kernel module, at least based on a file system table file within the computing device, via the at least one processor.

2. The method of claim 1, wherein the at least one input corresponds to enabling a barrier parameter or disabling a barrier parameter.

3. The method of claim 2, wherein, after enabling the barrier parameters, the at least one file system configuration enables slower and more stable file transfers within the memory of the computing device.

4. The method of claim 2, wherein when the barrier parameters are disabled, the at least one file system configuration enables faster file transfers within the memory of the computing device.

5. The method of claim 1, wherein the at least one processor is communicatively coupled to the bootloader.

6. The method of claim 5, further comprising using a bootloader via the at least one processor during the boot phase of the computing device to read the one or more flags stored in the factory reset protection module.

7. The method of claim 5, further comprising combining the one or more flags with a boot command line via the at least one processor, and using a bootloader to transmit the one or more flags to a kernel module.

8. A system comprising: A memory having one or more computer-readable instructions; as well as At least one processor communicatively coupled to memory, wherein the at least one processor executing the one or more computer-readable instructions stored in memory is configured to: Receive at least one input related to at least one file system configuration from the computing device via a user interface; Save one or more flags corresponding to the at least one input to the factory reset protection module of the computing device; The boot phase of initializing the computing device; Read one or more flags from the factory reset protection module of the computing device; Combine one or more of the flags with the boot command line; Send one or more flags, combined with the boot command line, to the kernel module of the computing device; Use the kernel module to update one or more default parameters defined in the file system table file, based at least on one or more of the aforementioned flags; as well as The kernel module is used to create the at least one file system configuration based on a file system table file within the computing device.

9. The system of claim 8, wherein the at least one input corresponds to enabling a barrier parameter or disabling a barrier parameter.

10. The system of claim 9, wherein, after enabling the barrier parameters, the at least one file system configuration enables slower and more stable file transfers within the memory of the computing device.

11. The system of claim 9, wherein when the barrier parameters are disabled, the at least one file system configuration enables faster file transfers within the memory of the computing device.

12. The system of claim 8, wherein the at least one processor is communicatively coupled to a bootloader.

13. The system of claim 12, wherein the at least one processor is configured to use a bootloader to read the one or more flags stored in the factory reset protection module during the boot phase of the computing device.

14. The system of claim 12, wherein the at least one processor is configured to combine the one or more flags with a boot command line and to use a bootloader to deliver the one or more flags to a kernel module.

15. A non-transitory machine-readable information storage medium, comprising one or more instructions that, when executed by at least one processor, perform operations including: Receive at least one input related to at least one file system configuration from the computing device; Save one or more flags corresponding to the at least one input to the factory reset protection module of the computing device; The boot phase of initializing the computing device; One or more flags are read from the factory reset protection module of the computing device during the boot phase of the computing device; Combine one or more of the flags with the boot command line; Send one or more flags, combined with the boot command line, to the kernel module of the computing device; Use the kernel module to update one or more default parameters defined in the file system table file, based at least on one or more of the aforementioned flags; as well as The kernel module is used to create the at least one file system configuration based on a file system table file within the computing device.

16. The non-transitory machine-readable information storage medium of claim 15, wherein the at least one input corresponds to an enabled barrier parameter or a disabled barrier parameter.

17. The non-transitory machine-readable information storage medium of claim 16, wherein, after enabling the barrier parameter, the at least one file system configuration enables slower and more stable file transfers within the memory of a computing device.

18. The non-transitory machine-readable information storage medium of claim 16, wherein when the barrier parameter is disabled, the at least one file system configuration enables faster file transfer within the memory of the computing device.

19. The non-transitory machine-readable information storage medium of claim 15, wherein the at least one processor is communicatively coupled to a bootloader, wherein the at least one processor is configured to use the bootloader to read the one or more flags stored in a factory reset protection module during the boot phase of a computing device.

20. The non-transitory machine-readable information storage medium of claim 19, wherein the at least one processor is configured to combine the one or more flags with a boot command line and to use a bootloader to deliver the one or more flags to a kernel module.

Images