invalidate_...pages2_range(9)

💖 NAME 💖

okay so bestie, this is invalidate_inode_pages2_range — and what it does is literally remove a range of pages from an address_space. that's the whole gig. main character energy for pagecache cleanup 💅

---

✨ SYNOPSIS ✨

int invalidate_inode_pages2_range (struct address_space *mapping ,
pgoff_t start , pgoff_t end );

---

🎀 ARGUMENTS 🎀

• mapping — the address_space in question. yes. that one. the space of addresses. 🦋
• start — the page offset 'from' which to invalidate. this is where the chaos begins, bestie.
• end — the page offset 'to' which to invalidate — and heads up, it's inclusive, so this one's invited to the party too 🫶

---

🌸 DESCRIPTION 🌸

so here's the tea ☕: any pages that get found mapped into pagetables? they get unmapped prior to invalidation. like, eviction notice first, then the actual yeeting. no page left hanging in a pagetable thinking it still has a home 😭 it's giving responsible cleanup, honestly. iconic behavior.

---

⭐ RETURN ⭐

returns -EBUSY if any pages could not be invalidated. that's it. that's the number. if it's all good, no -EBUSY for you, slay 🔥

---

🌈 SEE ALSO 🌈

the whole friend group, in the kernel file ./mm/truncate.c:

• folio_invalidate(9)
• mapping_evict_folio(9)
• truncate_inode_pages_range(9)
• truncate_inode_pages(9)
• truncate_inode_pages_final(9)
• mapping_try_invalidate(9)
• invalidate_mapping_pages(9)
• invalidate_inode_pages2(9)
• truncate_pagecache(9)
• truncate_setsize(9)
• pagecache_isize_extended(9)
• truncate_pagecache_range(9)

---

and that's the post 💌 this little masterpiece lives in ./mm, dated October 2026, and it's filed under invalidate_...pages2_range(9) — go off, pagecache queen 👑✨