clear_user_page(9)

💅 clear_user_page(9) — Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual, section 9 — this is the clear_user_page page and it's literally about clearing a page so it can be mapped into user space 🫶

---

🌸 NAME 🌸

clear_user_page — clear a page to be mapped to user space

---

✨ SYNOPSIS ✨

void clear_user_page (void *addr , unsigned long vaddr , struct page *page );

---

🎀 ARGUMENTS 🎀

• addr — the address of the page, periodt 💅
• vaddr — the address of the user mapping, iykyk
• page — the page. that's it. that's the page 🦋

---

💖 DESCRIPTION 💖

okay so here's the vibe: we condition the definition of clear_user_page on the architecture not having a custom clear_user_highpage. and why, you ask? 👀 because if there's some special flushing needed for clear_user_highpage, then it's likely that clear_user_page also needs some magic too 🔥 so like, they go together, no cap.

and honestly? since our only caller is the generic clear_user_highpage, not defining it is not much of a loss 🙈 like, it's giving "we're fine actually" energy fr fr.

---

👑 SEE ALSO 👑

Kernel file ./include/linux/highmem.h — yes bestie, that's where the lore lives 📖

• kmap(9)
• kunmap(9)
• kmap_to_page(9)
• kmap_flush_unused(9)
• kmap_local_page(9)
• kmap_local_folio(9)
• kmap_atomic(9)
• clear_user_pages(9)
• clear_user_highpage(9)
• clear_user_highpages(9)
• vma_alloc_zeroed_movable_folio(9)
• memcpy_from_folio(9)
• memcpy_to_folio(9)
• folio_zero_tail(9)
• folio_fill_tail(9)
• memcpy_from_file_folio(9)
• folio_zero_segments(9)
• folio_zero_segment(9)
• folio_zero_range(9)
• folio_release_kmap(9)

---

ngl bestie, that's a whole friend group of kmap and folio pages right there — go read them, they ate 💀✨

---

mwah 💋 this page lives in ./include/linux, dated October 2026, and it's literally called clear_user_page(9) ⭐ slay and goodbye ⭐ 🧚💜