![Re: [PATCH] OOM_pardon, a.k.a. don't kill my xlock (2004)](https://techtrendtrove.com/wp-content/uploads/2026/06/re-patch-oom-pardon-a-k-a-don-t-kill-my-xlock-2004-featured.jpg)
TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
In September 2004, Linux kernel developer Andries Brouwer discussed a patch to prevent the OOM killer from terminating essential processes such as xlock. The proposal highlights ongoing challenges in process management during memory shortages and raises questions about system stability and administrator control.
In September 2004, a Linux kernel developer responded to a patch proposal that seeks to prevent the out-of-memory (OOM) killer from terminating critical processes such as xlock, highlighting ongoing concerns about process management during memory shortages.
The discussion centers on a patch titled ‘OOM_pardon,’ proposed by Thomas Habets, which suggests implementing a sysctl setting that would prevent the kernel’s OOM killer from killing certain processes. The idea is to allow system administrators to specify processes that should be immune to termination when the system runs out of memory.
Andries Brouwer, in his reply, acknowledged the proposal but emphasized that the kernel currently lacks a straightforward way to protect specific processes from being killed during OOM conditions. He explained that the kernel’s existing mechanisms are designed to free memory quickly, often without discrimination, to prevent system crashes.
The conversation includes an analogy about aircraft fuel management, illustrating the complexity of process prioritization during resource shortages. Brouwer’s response suggests that implementing process-specific protections could complicate the kernel’s memory management strategies.
Why It Matters
This development matters because it highlights the ongoing challenge of balancing system stability with the need to protect critical processes during low-memory conditions. If implemented, such a patch could give administrators more control over process management, potentially preventing disruptions caused by the OOM killer. However, it also raises concerns about system stability and predictability, especially if critical processes are shielded from termination during resource shortages.
As an affiliate, we earn on qualifying purchases.
Background
In Linux systems, the OOM killer is a mechanism that terminates processes to free memory when the system is critically low. Historically, it targets processes based on heuristics, which can sometimes include essential or user-critical processes. The proposal for a ‘don’t kill my xlock’ patch reflects a desire for finer control over this behavior, which has been a topic of debate among kernel developers and system administrators for years.
In 2004, discussions around process management and resource allocation were ongoing, with developers exploring ways to improve system resilience without compromising stability. The patch proposal is part of broader efforts to refine kernel memory management and process prioritization.
“The kernel currently lacks a straightforward way to protect specific processes from being killed during OOM conditions.”
— Andries Brouwer
“A sysctl that prevents the OOM killer from terminating certain processes would give administrators more control during low-memory situations.”
— Thomas Habets
system memory monitoring software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It remains unclear whether the proposed patch will be accepted or implemented in the Linux kernel. The technical feasibility and potential impact on system stability are still under discussion, and no final decision has been made.
As an affiliate, we earn on qualifying purchases.
What’s Next
Further discussions among kernel developers are expected to evaluate the technical challenges of implementing process-specific protections. Monitoring of the patch’s progress and community feedback will determine if it advances toward inclusion in future kernel releases.
server resource control software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the main goal of the ‘OOM_pardon’ patch?
The patch aims to prevent the Linux kernel’s out-of-memory (OOM) killer from terminating specific processes, such as xlock, during low-memory situations, giving administrators more control.
Why is protecting processes from the OOM killer important?
Protecting critical or user-important processes can prevent system disruptions and maintain stability during memory shortages, especially for processes that are essential for system operation or user experience.
What are the potential risks of implementing such a patch?
Allowing certain processes to be immune from the OOM killer could lead to system instability, as unkillable processes may prevent the kernel from freeing enough memory, potentially causing system crashes or hangs.
Has this patch been accepted into the Linux kernel?
No, as of now, the patch remains a proposal under discussion, with no consensus on its adoption or implementation.
Source: Hacker News
Evergreen bestsellers Picks
bestsellers
As an affiliate, we earn on qualifying purchases.
