Skip to contentSkip to conversation

docs-cgroup-document-empty-write-behavior-of-memory-limit-knobs.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Oct 7

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: docs: cgroup: document empty-write behavior of memory limit knobs
has been removed from the -mm tree. Its filename was
docs-cgroup-document-empty-write-behavior-of-memory-limit-knobs.patch

This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Tao Cui <[email protected]>
Subject: docs: cgroup: document empty-write behavior of memory limit knobs
Date: Wed, 26 Aug 2026 10:17:53 +0800

A maintenance script on a cluster wrote an unset variable into memory.max of a workload cgroup; the variable expanded to an empty string, the write succeeded, and the workload in the cgroup was OOM-killed. Nothing pointed back at the write, so it took quite some time to trace the OOM kills to that script.

The memory controller documentation does not say what an empty write does; the cpuset controller documents its empty-value semantics. The actual behavior is that the empty string is accepted as 0. Reproduced on a k8s cluster (v1.29, cgroup v2, two-container pod, 384M limit):

# LIMIT=

  # echo "$LIMIT" > $CG/memory.max
  # echo $?
  0

m6demo 0/2 OOMKilled 0

Memory cgroup out of memory: Killed process 339529 (sleep) ... anon-rss:32kB

State it where the interface files are introduced, alongside the existing notes on units and page rounding.

---

 Documentation/admin-guide/cgroup-v2.rst |    4 ++++
 1 file changed, 4 insertions(+)
Documentation/admin-guide/cgroup-v2.rst renamed from Documentation/admin-guide/cgroup-v2.rst~docs-cgroup-document-empty-write-behavior-of-memory-limit-knobs +4 -0
@@ -1321,6 +1321,10 @@ All memory amounts are in bytes.  If a v
 PAGE_SIZE is written, the value may be rounded up to the closest
 PAGE_SIZE multiple when read back.
 
+For the limit files described below, an empty or all-whitespace
+write is accepted and sets the limit to 0.  To disable a limit,
+write "max"; to set it to zero explicitly, write "0".
+
   memory.current
 	A read-only single value file which exists on non-root
 	cgroups.

_

Patches currently in -mm which might be from [email protected] are