freeze_kernel_threads(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ freeze_kernel_threads β€” a.k.a. "go to the refrigerator" ✨

Ok so bestie, welcome to the freeze_kernel_threads(9) page from the Kernel API Manual πŸ’… this one's short and sweet, but it's lowkey important so like… pay attention 🫢


πŸŽ€ NAME πŸŽ€

freeze_kernel_threads β€” literally just making freezable kernel threads go to the refrigerator 🧊✨

Like yes, that's the whole vibe. The kernel threads get sent to chill. No cap.


🌸 SYNOPSIS 🌸

int freeze_kernel_threads (void );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” no arguments, bestie. None. Zero. Not a single one πŸ™ˆ it just takes nothing and does its thing.

πŸ’– DESCRIPTION πŸ’–

Okay so here's the tea β˜• on success it returns 0 β€” iconic, we love a clean return πŸ’…

But on failure? It returns -errno, and ⚠️ only the kernel threads are thawed β€” not the userspace tasks. Ngl this is on purpose: it gives the caller a chance to do any additional cleanups (if any) before thawing the userspace tasks. So basically the kernel threads come out of the fridge first and everyone else is still chilling 🧊

So, heads up: it is the responsibility of the caller to thaw the userspace tasks, when the time is right πŸ‘‘ like the caller is the main character here and has to handle that part. Periodt.


πŸ‘‘ SEE ALSO πŸ‘‘


That's literally the whole page, bestie πŸ’œ short king of a manpage fr fr. Go thaw those userspace tasks when the time is right, ok? 🫢

This little gem lives in ./kernel/power 🌈 dated October 2026 πŸŽ€ β€” mwah, bye! πŸ’‹βœ¨

πŸ“¦ where this page comes from