follow_pfnmap_end(9)

💖 follow_pfnmap_end(9) 💖

okay so this is follow_pfnmap_end, straight out of the Kernel API Manual — think of it as the closing bracket of the follow_pfnmap_start() saga 🎀

✨ NAME ✨

follow_pfnmap_end — the "and that's a wrap bestie" half of a follow_pfnmap_start() process 💅

✨ SYNOPSIS ✨

void follow_pfnmap_end (struct follow_pfnmap_args *args );

✨ ARGUMENTS ✨

• args — a pointer to struct follow_pfnmap_args, aka the lil context object you're handing over 🫶

✨ DESCRIPTION ✨

so here's the tea 🍓 — this one must be used as a pair with follow_pfnmap_start. literally a matching set, no cap 👑. and if you wanna know more, go read the start function above, it's got all the extra info you need ✨

no like fr, they're a pair — don't leave a follow_pfnmap_start() hanging, that's not the vibe 💀

🌈 SEE ALSO 🌈

Kernel file ./mm/memory.c — and honestly the whole friend group shows up here, so let me introduce everyone 🧚:

• free_pgd_range(9)
• free_pgtables(9)
• __vm_normal_page(9)
• vm_normal_page(9)
• vm_normal_folio(9)
• vm_normal_page_pmd(9)
• vm_normal_folio_pmd(9)
• vm_normal_page_pud(9)
• restore_exclusive_pte(9)
• cond_install_uffd_wp_ptes(9)
• zap_vma_for_reaping(9)
• unmap_vmas(9)
• zap_vma_range_batched(9)
• zap_vma_range(9)
• zap_special_vma_range(9)
• vm_insert_pages(9)
• vm_insert_page(9)
• vm_map_pages(9)
• vm_map_pages_zero(9)
• vmf_insert_pfn_prot(9)
• vmf_insert_pfn(9)
• remap_pfn_range(9)
• vm_iomap_memory(9)
• __vmf_anon_prepare(9)
• finish_mkwrite_fault(9)
• unmap_mapping_folio(9)
• unmap_mapping_pages(9)
• unmap_mapping_range(9)
• set_pte_range(9)
• finish_fault(9)
• mm_account_fault(9)
• follow_pfnmap_start(9)
• generic_access_phys(9)
• access_remote_vm(9)
• copy_remote_vm_str(9)
• folio_zero_user(9)

and that's the whole page, bestie, ate and left no crumbs 🔥 — brought to you by the fine folks at ./mm, dated October 2026, signing off 💜🦋