mmap_action_complete(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 mmap_action_complete — NAME 🌸

okay so bestie, this is mmap_action_complete from the Kernel API Manual (section 9, the big-kid kernel-functions section, iykyk), and it does exactly one thing: it executes a VMA descriptor action ✨

🎀 SYNOPSIS 🎀

int mmap_action_complete (struct vm_area_struct *vma , struct
       mmap_action *action , bool is_compat );

like, yes, it takes three things and gives you back an int. she's lowkey simple. 🫶

💖 ARGUMENTS 💖

  • vma — the VMA you're doing the action upon. she's the main character of this call 💅
  • action — the action itself. this is the thing that's actually gonna happen.
  • is_compat — is this being invoked from the compatibility layer? yes/no, that's the whole vibe check. 👑

✨ DESCRIPTION ✨

Similar to mmap_action_prepare.

that's it. that's the whole description. not me expecting a whole essay and getting one line 😭 literally the most mysterious queen in the kernel API, no cap. if you wanna know how it works, go read mmap_action_prepare (she's in SEE ALSO, obvs 🎀).

🔥 RETURN 🔥

  • 0 on success 🎉 slay, we ate, nothing to worry about
  • or error — and bestie, listen, this part matters: at which point the VMA will be unmapped if !is_compat. so if you're not coming from the compat layer and this thing errors out, the VMA gets unmapped. no VMA for you. 💀 keep that in mind fr fr.
⚠️ real talk: on error with !is_compat, the VMA is gone. that's not a vibe, that's just the contract.

🦋 SEE ALSO 🦋

kernel file ./mm/util.c 💜 and literally the whole friend group:

✨ and that's the page, bestie ✨ this one came from source ./mm, dated October 2026, filed under the Kernel API Manual — go forth and complete your actions responsibly 💅🎀💖

📦 where this page comes from