![Re: [PATCH] OOM_pardon, a.k.a. don't kill my xlock (2004)](https://theideamagazine.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 by developer Andries Brouwer seeks to stop the Out-Of-Memory (OOM) killer from killing certain processes, including xlock. The development highlights ongoing efforts to improve kernel memory management and stability.
A patch has been proposed to the Linux kernel to prevent the Out-Of-Memory (OOM) killer from terminating certain processes, such as xlock, during memory shortages. The development was shared by Linux kernel developer Andries Brouwer on September 24, 2004, and aims to address concerns about process termination in critical or user-facing applications.
The patch, titled ‘oom_pardon,’ was communicated via email by Brouwer to the Linux kernel mailing list. It introduces a mechanism allowing specific processes to be marked as immune from the OOM killer, which typically terminates processes when system memory is critically low. The proposal was motivated by the desire to protect processes like xlock, which are important for user experience or system stability in certain contexts.
According to Brouwer, the patch would enable administrators or developers to specify processes that should not be killed during memory pressure, effectively creating a safeguard against unwanted termination. The patch is still in review, and its implementation details are being discussed among kernel developers.
Why It Matters
This development is significant because it addresses a core challenge in Linux system stability: balancing memory management with process continuity. By allowing certain processes to be protected from the OOM killer, systems can maintain essential services and user interfaces even under extreme memory conditions. However, it also raises questions about potential abuse or system stability if critical processes are protected indiscriminately.
Linux server memory management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The OOM killer is a Linux kernel mechanism activated when the system runs out of memory, designed to free resources by terminating less critical processes. Historically, this has been a blunt but necessary tool, sometimes leading to unintended disruptions. The idea of ‘pardon’ mechanisms or process exemptions has been discussed in kernel development circles for years, but no widespread implementation exists as of this development.
This proposal follows ongoing efforts to refine Linux memory management, especially as systems become more complex and user-focused. It echoes previous debates about how best to handle critical processes during resource shortages without compromising overall system stability.
“The patch would enable administrators to specify processes that should not be killed during memory pressure, protecting critical applications like xlock.”
— Andries Brouwer
process monitoring software for Linux
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear how widely accepted or adopted this patch will become, or what potential side effects might arise from exempting processes from the OOM killer. The technical details are still under discussion, and the impact on overall system stability remains to be evaluated.
As an affiliate, we earn on qualifying purchases.
What’s Next
The patch is currently under review by the Linux kernel community. Future steps include further testing, feedback from kernel developers, and potential integration into official kernel releases. Additional discussions may address scope and safeguards for process exemptions.
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 OOM killer from terminating specific, critical processes during memory shortages, thereby improving system stability and user experience.
Which processes can be protected using this patch?
Processes like xlock, which are important for user interface or system stability, could be marked as protected from being killed during memory pressure.
Does this patch eliminate the need for the OOM killer?
No, it does not eliminate the OOM killer but provides a way to exempt certain processes from its actions during critical situations.
Are there risks associated with exempting processes from the OOM killer?
Yes, if critical processes are protected indiscriminately, it could lead to system instability or failure to recover from low-memory conditions.
Source: Hacker News
