exit_oom_victim(9)

💅 exit_oom_victim(9) 💅

okay bestie, welcome to the Kernel API Manual ✨ — this lil page is about exit_oom_victim, and honestly? iconic behaviour from a function with zero arguments.

---

🌸 NAME 🌸

exit_oom_victim — note the exit of an OOM victim

like, it literally just marks down that an OOM victim has peaced out. that's the whole vibe. 💀

---

✨ SYNOPSIS ✨

void exit_oom_victim (void );

one function, no drama, void in and void out. slay. 🫶

---

🎀 ARGUMENTS 🎀

• void — no arguments 🦋

literally none. zero. it's giving "I need nothing from you, I'm built different". no params to pass, no structs to fill, no pointers to babysit. main character energy fr fr. 😭

---

🌈 SEE ALSO 🌈

bestie, go read these next, they're all in the kernel file ./mm/oom_kill.c and they're lowkey all connected 👑

• oom_cpuset_eligible(9)
• oom_badness(9)
• dump_tasks(9)
• mark_oom_victim(9)
• oom_killer_enable(9)
• oom_killer_disable(9)
• out_of_memory(9)

the way this whole little friend group lives in ./mm/oom_kill.c… obsessed. 💖

---

🧚 quick vibe check: this page has no options, no env vars, no exit statuses and no warnings to report — the source page simply doesn't list any, so don't come for me, I'm just the messenger. 🙈

---

and that's the page, babe! 🍓 source is ./mm (the whole mm directory, mwah), dated October 2026, and it's exit_oom_victim(9) — catch you in the group chat 💅💜🔥