cap_vm_enough_memory(9)

📦 version 7.3.1, in nixpkgs unstable

✨ cap_vm_enough_memory(9) ✨

okay bestie, welcome to the Kernel API Manual 💅 today we're looking at cap_vm_enough_memory from the cap_* family — yes, the whole friend group is in SEE ALSO, we'll get there 🫶

🌸 NAME 🌸

cap_vm_enough_memory — Determine whether a new virtual mapping is permitted ✨

Like, the vibe check for "can this task please have some more virtual memory" 🎀

🦋 SYNOPSIS 🦋

int cap_vm_enough_memory (struct mm_struct *mm , long pages );

Two args, no cap, that's the whole signature 💖

💜 ARGUMENTS 💜

  • mm — The VM space in which the new mapping is to be made. the address space we're asking about 🧚
  • pages — The size of the mapping. in pages, obvi 🍓

🌈 DESCRIPTION 🌈

Determine whether the allocation of a new virtual mapping by the current task is permitted. that's literally it, that's the whole plot 😭 the current task wants a new virtual mapping and this function is the one deciding if that's allowed to happen 💅

⭐ RETURN ⭐

  • 0 if permission granted 👑
  • negative error code if not 💀

so like, zero means slay, negative means not slay, iykyk 🫶

🎀 SEE ALSO 🎀

Kernel file ./security/commoncap.c and the entire cap squad, fr fr:

that's twenty-two (22) siblings bestie, main character energy all around 🌸

so yeah, that's the whole page — short and iconic, lowkey one of the easiest reads in the manual 💖

sign-off time 🎀 this lil page comes from ./security and it's dated October 2026 — and the manual calls itself cap_vm_enough_memory(9) all over again at the bottom like a little mirror selfie 🪞 stay hydrated, read your manpages, mwah 💋

📦 where this page comes from