vma_anon_address(9)

💅 vma_anon_address(9) — bestie edition 💅

okay so this page is straight out of the Kernel API Manual, and it's giving “where does this anonymous page range actually live in virtual memory?” energy. let's get into it 🦋

🌸 NAME 🌸

vma_anon_address — find the virtual address an anonymous page range is mapped at. no cap, that's the whole vibe ✨

🎀 SYNOPSIS 🎀

unsigned long vma_anon_address (const struct vm_area_struct *vma ,
       pgoff_t pgoff_anon , unsigned long nr_pages );

💖 ARGUMENTS 💖

• vma — the VMA which maps this object. she's the main character of the mapping situation 👑
• pgoff_anon — the anonymous page index belonging to the folio. literally the page's little name tag 🍓
• nr_pages — the number of pages to consider. the page count, bestie 🔢

🔥 DESCRIPTION 🔥

okay important caveat incoming: this is only valid for anonymous or MAP_PRIVATE-mapped file-backed VMAs. that's the whole validity situation, don't come for me with other VMA types 😭

⭐ RETURN ⭐

if any page in this range is mapped by this VMA, it returns the first address where any of these pages appear. slay ✨

otherwise? it returns -EFAULT. and that's on periodt 💅

🦋 SEE ALSO 🦋

• Kernel file ./mm/internal.h
• folio_pte_batch_flags(9)
• pte_move_swp_offset(9)
• pte_next_swp_offset(9)
• swap_pte_batch(9)
• sync_with_folio_pmd_zap(9)
• folio_evictable(9)
• vma_filebacked_address(9)

signed off by your ./mm source bestie, version vma_anon_address(9), dated October 2026 💋🫶