memory_failure_pfn(9)

💖 memory_failure_pfn (9) — Kernel API Manual 💖

okay so bestie, welcome to the memory_failure_pfn(9) page, brought to you by the Kernel API Manual ✨ this one is all about handling a memory failure on a page that's not backed by struct page — yes, that's the whole vibe, and honestly it's giving niche-but-important 🎀

---

🌸 NAME 🌸

memory_failure_pfn — Handle memory failure on a page not backed by struct page.

like literally, a page with no struct page backing it. that's the assignment. slay 💅

---

✨ SYNOPSIS ✨

int memory_failure_pfn (unsigned long pfn , int flags );

two arguments, one int coming back at you. no cap, that's it 🦋

---

🫶 ARGUMENTS 🫶

• pfn — Page Number of the corrupted page. yep, the Page Number of the page that's gone bad 😭 that's the one we're here about.
• flags — fine tune action taken. it literally fine-tunes the action, bestie — that's the whole job 🔥

---

👑 RETURN 👑

• 0 — success 🎉 everything's fine, we ate.
• -EBUSY — Page PFN does not belong to any address space mapping. 💀 so the Page PFN isn't mapped to any address space, and the call just can't do its thing. not a vibe, but at least you know why.

ngl the original lays these two out in one squished line, so here they are un-squished for your reading pleasure — the facts are exactly the same, promise 🫶

---

🌈 SEE ALSO 🌈

go read these next, iykyk ✨

• Kernel file ./mm/memory-failure.c
• MF_ATTR_RO(9)
• get_hwpoison_page(9)
• mf_dax_kill_procs(9)
• memory_failure(9)
• memory_failure_queue(9)
• unpoison_memory(9)
• soft_offline_page(9)

---

aaaand that's the whole page, bestie 🧚💜 this icon lives in ./mm and the manual's dated October 2026 — so go forth, handle those failures, and remember: page not backed by struct page? now you know exactly who to call 📞✨ periodt.