folio_remove_rmap_pud(9)

🦋 folio_remove_rmap_pud(9) 🦋

okay bestie, welcome to the Kernel API Manual entry for folio_remove_rmap_pud(9) — we're literally removing a PUD mapping from a page range of a folio, and it's giving kernel-core main character energy 💅✨

🌸 NAME 🌸

folio_remove_rmap_pud — remove a PUD mapping from a page range of a folio 🫶

✨ SYNOPSIS ✨

void folio_remove_rmap_pud (struct folio *folio , struct page *page , struct vm_area_struct *vma );

🎀 ARGUMENTS 🎀

• folio — the folio you're removing the mapping from, bestie 💖
• page — the first page to remove 👑
• vma — the vm area from which the mapping is removed ✨

💖 DESCRIPTION 💖

so the page range of the folio is defined by [page, page + HPAGE_PUD_NR) — that's the exact range, no cap 📏

⚠️ the caller needs to hold the page table lock. like, actually hold it. 🔒

🔥 SEE ALSO 🔥

Kernel file ./mm/rmap.c is the spot, and the whole friend group is here:

• __anon_vma_prepare(9)
• anon_vma_clone(9)
• unlink_anon_vmas(9)
• page_address_in_vma(9)
• folio_referenced(9)
• mapping_wrprotect_range(9)
• pfn_mkclean_range(9)
• folio_move_anon_rmap(9)
• __folio_set_anon(9)
• __page_check_anon_rmap(9)
• folio_add_anon_rmap_ptes(9)
• folio_add_anon_rmap_pmd(9)
• folio_add_new_anon_rmap(9)
• folio_add_file_rmap_ptes(9)
• folio_add_file_rmap_pmd(9)
• folio_add_file_rmap_pud(9)
• folio_remove_rmap_ptes(9)
• folio_remove_rmap_pmd(9)
• try_to_unmap(9)
• try_to_migrate(9)
• make_device_exclusive(9)
• __rmap_walk_file(9)

xoxo, this page came from ./mm and it's dated October 2026 — mwah 💋🌸