freezer_fork(9)

📦 version 7.3.1, in nixpkgs unstable

💖 freezer_fork(9) 💖

okay bestie, welcome to the <pink>freezer_fork</pink> page from the Kernel API Manual — yes we're in the kernel docs now, and honestly? we're slaying 🧊✨

🌸 NAME 🌸

freezer_fork — the cgroup post-fork callback, aka the little function that shows up right after a task gets forked 🫶

✨ SYNOPSIS ✨

void freezer_fork (struct task_struct *task );

that's it, that's the whole signature — void, one argument, iconic behaviour 💅

🎀 ARGUMENTS 🎀

  • task — a task which has just been forked. literally brand-new, fresh out the fork, main character energy 👑

🦋 DESCRIPTION 🦋

so task has just been created (congrats to it 🎉) and it should conform to the current state of the cgroup_freezer it belongs to. like, it needs to match the vibe of its cgroup freezer, periodt.

now here's the spicy part 🌶️ — this function may race against freezer_attach. and if we lose that race? honestly no big deal, we don't have to do anything 💀 because freezer_attach will put task into the appropriate state itself. so losing here is lowkey a win, we just vibe and let freezer_attach handle it 🫶

no cap, the race is real, but the outcome's fine either way — just know who's doing the actual state-setting 😌

👑 SEE ALSO 👑

Kernel file ./kernel/cgroup/legacy_freezer.c plus the whole freezer friend group:

go read them, iykyk 📚✨

aaaaand that's the page!! 🌈 mwah 💋 this one lives in ./kernel/cgroup and it's dated October 2026 — so mark your calendar bestie, future vibes only 🔥👑💜

📦 where this page comes from