Patching System Calls for Data Protection via Write Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection systems in computing environments face challenges in providing additional functionality for system calls, as they are limited by default kernel functions, which restrict backup and restore operations across different operating systems and devices.
Innovation Solution
The solution involves patching system calls with custom service routines, allowing for the execution of additional functions by trapping and redirecting system calls to customized service routines while maintaining availability of default functions, enabling operations like write tracking and incremental backups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If default system calls are used in the kernel space, then the system maintains stability and compatibility across different operating systems, but additional functionality for data protection operations cannot be achieved
Solution Approach 1:
A write tracking driver is introduced as an intermediary component between the backup application and the block device. This driver intercepts system calls and provides additional data protection functionality through write tracking operations, while maintaining compatibility with the existing kernel architecture and default system calls.
Solution Approach 2:
The system is segmented into distinct functional components: the default kernel space that maintains system stability, and a separate write tracking driver that provides additional data protection functionality. This segmentation allows each component to operate independently with its own functionality.
2Adaptability or versatility
If custom service routines are implemented to provide additional functionality, then data protection operations are enhanced, but the complexity of the system increases
Solution Approach 1:
The write tracking driver is designed as a universal component that can be integrated with existing backup applications and block devices. It provides multiple functions including write tracking, backup operations, and restore operations through a unified interface, reducing the need for separate custom implementations.
Solution Approach 2:
The write tracking driver automatically tracks writes to block devices and manages backup operations without requiring complex external control. It self-manages the tracking of written data blocks and coordinates with backup applications to perform incremental backups efficiently.
3Adaptability or versatility
If system calls are patched to redirect to custom routines, then additional operations like write tracking are enabled, but the difficulty of maintaining and managing system calls increases
Solution Approach 1:
The write tracking driver is loaded and initialized before backup operations begin. It pre-establishes the tracking mechanisms and interceptors for system calls, so that when backup operations are performed, the additional functionality is already in place and does not require complex runtime modifications.
Solution Approach 2:
The driver acts as an intermediary layer that intercepts system calls through a standardized interface. This intermediary approach allows the system to maintain default system call handling while adding tracking functionality, avoiding the need to patch or modify existing system calls directly.
Data Source
AI summary
Systems and methods for patching system calls issued on a device. System calls are patched by transforming system calls to provide additional functionality. The system calls can then be rerouted to the updated or custom functions.