![Re: [PATCH] OOM_pardon, a.k.a. don't kill my xlock (2004)](https://artificialintelligencemax.com/wp-content/uploads/2026/06/re-patch-oom-pardon-a-k-a-don-t-kill-my-xlock-2004-featured.jpg)
TL;DR
A Linux kernel patch proposed in September 2004 seeks to stop the kernel from killing important processes such as xlock during out-of-memory situations. The development is confirmed through developer emails, highlighting efforts to improve system stability.
Developers confirmed the existence of a Linux kernel patch, ‘oom_pardon,’ designed to prevent essential processes like xlock from being terminated during out-of-memory (OOM) events, addressing a longstanding stability concern.
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
On September 24, 2004, Andries Brouwer, a Linux kernel developer, responded to a proposal by Thomas Habets regarding a new sysctl feature intended to protect critical processes from being killed during OOM situations. The patch, named ‘oom_pardon,’ aims to modify the kernel’s OOM killer behavior, ensuring that processes deemed essential are spared when memory is exhausted.
Habets had suggested a mechanism where the kernel would avoid killing certain processes, or at least escalate to a panic if no other options exist, to prevent system crashes caused by the termination of vital services like xlock, a graphical lock screen utility. Brouwer’s confirmation indicates that the patch was under active consideration as of late September 2004, with developers exploring ways to improve process survivability under memory pressure.
Why It Matters
This development matters because it addresses a critical stability issue in Linux systems, where the OOM killer could terminate essential processes, leading to system crashes or loss of service. Protecting key processes enhances reliability, especially in production environments where uptime is crucial.
Products Worth Considering
Samsung 57 Odyssey Neo G9 (G95NC) Dual 4K UHD 1000R Curved Gaming Monitor
LG UltraGear 32GX870A-B 32-inch 4K UHD OLED Gaming Monitor
Samsung Odyssey G7 G75F 40-Inch WUHD Curved Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Background
Prior to this discussion, the Linux kernel’s OOM killer would indiscriminately terminate processes when memory was exhausted, sometimes killing vital services and causing system instability. The proposal of ‘oom_pardon’ reflects ongoing efforts to refine memory management and process prioritization in Linux, a topic of interest among kernel developers for years. The correspondence from September 2004 indicates active exploration of solutions to this problem.
“The kernel should avoid killing critical processes like xlock during OOM events, and we are considering a patch to implement this.”
— Andries Brouwer
“A sysctl to prevent essential processes from being killed during OOM would be a valuable addition.”
— Thomas Habets
What Remains Unclear
It is not yet clear whether the ‘oom_pardon’ patch was accepted into the mainline kernel or how widely it was implemented, as the correspondence indicates ongoing development and discussion.
What’s Next
Following this discussion, developers would need to finalize the patch, test its impact on system stability, and determine its inclusion in future kernel releases. Further updates on the patch’s adoption and implementation status are expected in subsequent kernel development cycles.
Key Questions
What is the ‘oom_pardon’ patch?
The ‘oom_pardon’ patch is a proposed Linux kernel modification aimed at preventing critical processes from being killed during out-of-memory conditions.
Why is protecting processes like xlock important?
Protecting processes like xlock ensures system stability and availability, especially during memory shortages, preventing crashes caused by unwanted process termination.
Did the patch get integrated into the Linux kernel?
It is not confirmed whether the patch was accepted into the mainline kernel; the discussion from September 2004 indicates ongoing evaluation.
What are the potential risks of implementing such a patch?
Potential risks include complicating the kernel’s OOM management, possibly leading to situations where critical processes are protected at the expense of overall system stability or memory management efficiency.
Source: Hacker News
