vma_alloc_folio(9)

✨ NAME ✨

okay so this is vma_alloc_folio(9), straight from the Kernel API Manual, bestie — and it's literally about allocating a folio for a VMA. iconic behavior, no cap 💅

---

🦋 SYNOPSIS 🦋

       struct folio * vma_alloc_folio (gfp_t gfp , int order , struct
       vm_area_struct *vma , unsigned long addr );

---

🌸 ARGUMENTS 🌸

• gfp — the GFP flags, fr fr. they matter.
• order — the order of the folio. yes bestie, order.
• vma — a pointer to the VMA. main character pointer energy.
• addr — the virtual address of the allocation. it must be inside vma — like, non-negotiable, okay? 🙈

---

🎀 DESCRIPTION 🎀

So what this does is allocate a folio for a specific address in vma, using the appropriate NUMA policy. slay.

💀 but listen: the caller must hold the mmap_lock of the mm_struct of the VMA to prevent it from going away. that's not a vibe check you can skip, bestie — it's required.

You should use this for all allocations for folios that will be mapped into user space, excepting hugetlbfs, and excepting where direct use of folio_alloc_mpol is more appropriate. iykyk ✨

---

💖 RETURN 💖

The folio on success 🫶 or NULL if allocation fails 😭. that's the whole return section, periodt.

---

🌈 SEE ALSO 🌈

• Kernel file ./mm/mempolicy.c
• numa_nearest_node(9)
• nearest_node_nodemask(9)
• folio_can_map_prot_numa(9)
• alloc_pages_mpol(9)
• alloc_pages(9)
• mpol_misplaced(9)
• mpol_shared_policy_init(9)
• mpol_parse_str(9)
• mpol_to_str(9)

---

kisses bestie 💋 this whole little page comes from source ./mm, dated October 2026, and the title is vma_alloc_folio(9) — and that's the cute sign-off, mwah 🎀🦋💜