Kernel Update Application Without System Restart

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Updating a kernel of an operating system typically requires restarting the computing system, causing downtime and revenue loss for businesses, as existing solutions fail to apply updates without system restarts, especially when data structures in memory need to be updated.

Innovation Solution

The introduction of a Fix Management Domain (FMD) that monitors and applies updates only when specific conditions are met, avoiding immediate system restarts by checking instance-counts of data structures and applying updates when they are not in memory, thus ensuring stability without downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the kernel update is applied immediately, then the system reliability is improved, but the system stability deteriorates due to potential data structure conflicts in memory

Engineering Contradiction:
Improvesystem reliabilityVSAvoidsystem stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system performs preliminary checks before applying the kernel update by examining structure change information to identify affected data structures. It then proactively suspends operations that would create instances of these data structures in memory, preventing conflicts before they occur. This preliminary action enables safe update application without system restart.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism that mediates between the update application process and the running system operations. This intermediary monitors data structure usage, controls instance creation, and coordinates the update application timing, allowing the system to maintain stability while improving reliability through updated kernel code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system is restarted to apply the update, then the update is successfully applied, but the downtime increases causing revenue loss

Engineering Contradiction:
Improveupdate application successVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of the kernel update to identify affected data structures and their usage patterns before applying the update. This advance preparation enables the system to plan the update application strategy, preventing the need for system restart and eliminating associated downtime while ensuring successful update application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the operational parameters of the system by dynamically controlling data structure instance creation and managing memory allocation during the update process. By adjusting these parameters, the system can apply kernel updates in-place without restart, transforming the traditional update model from disruptive to continuous operation.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the instance-count check is performed for all data structures, then the update safety is improved, but the processing complexity increases

Engineering Contradiction:
Improveupdate safetyVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the critical information needed for safe update application by analyzing structure change information to identify affected data structures. Rather than checking all data structures uniformly, it extracts and monitors only those specifically impacted by the kernel update, reducing processing complexity while maintaining update safety through targeted instance-count verification.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different levels of monitoring and control to different data structures based on their relevance to the current kernel update. High-priority data structures with structure changes receive detailed instance-count checking and control, while unrelated data structures are excluded from intensive monitoring. This local quality approach improves update safety for critical structures without uniformly increasing processing complexity across all data structures.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11663072B2Avoid system restart after applying fixes
Publication Date: 2023.05.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11663072B2 patent drawing
  • US11663072B2 patent drawing
  • US11663072B2 patent drawing

AI summary

A computer-implemented method includes receiving, by a computing system, an update for a computer program executing on the computing system. The method further includes determining, by the computing system, a data structure that is affected by the update by checking a structure change information included in the update. The method further includes checking, by the computing system, instance-count of the data structure, the instance-count representing a number of instances of the data structure in a memory of the computing system. The method further includes based on a determination that the instance-count is zero, applying, by the computing system, the update to the computer program.