mem_cgroup_get_oom_group(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mem_cgroup_get_oom_group(9) 💖

okay so this is a page from the Kernel API Manual, and honestly? it's a little baddie. it's called mem_cgroup_get_oom_group and it's giving "who do we gotta yeet when memory runs out" energy. let's get into it 🫶

✨ NAME ✨

mem_cgroup_get_oom_group — get a memory cgroup to clean up after OOM

like, literally what the name says bestie, it grabs you the memcg that needs the cleanup after an out-of-memory situation 💅

🌸 SYNOPSIS 🌸

struct mem_cgroup * mem_cgroup_get_oom_group (struct task_struct *victim
, struct mem_cgroup *oom_domain );

look at that signature, she's iconic 🔥

🎀 ARGUMENTS 🎀

  • victim — the task that the OOM killer is gonna kill 😭 that's the whole vibe, it's the sacrifice
  • oom_domain — the memcg when it's a memcg OOM, or NULL when it's a system-wide OOM. two moods, one param 🦋

💜 DESCRIPTION 💜

So it returns a pointer to a memory cgroup, right? and that cgroup has to be cleaned up by killing all the belonging OOM-killable tasks. no cap, that's the job, that's the assignment 💀

⚠️ important bestie: the caller has to call mem_cgroup_put on the returned non-NULL memcg. not "should", not "maybe" — has to. don't leave her hanging 🙈

🌈 SEE ALSO 🌈

okay this list is LONG, she ate and left no crumbs 👑. Kernel file ./mm/memcontrol.c, plus:

and that's the whole page, bestie!! ✨ source is ./mm, dated October 2026, and this little moment of kernel lore is officially over 💖 go call mem_cgroup_put like the good noodle you are 🧚🌟

📦 where this page comes from