kmsan_iounmap_page_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kmsan_iounmap_page_range β€” bestie, it's KMSAN cleanup time

Okay so real quick, this is section 9 of the Kernel API Manual, the kmsan_iounmap_page_range page, and honestly? It's a short one. A cute little one. Let's get into it πŸŽ€


✨ NAME ✨

kmsan_iounmap_page_range β€” the function that pops into KMSAN's DMs to let it know a iounmap_page_range() call is happening. That's it. That's the job. She's a notifier, she's a messenger, she's not doing the actual unmapping herself πŸ’…


🌸 SYNOPSIS 🌸

void kmsan_iounmap_page_range (unsigned long start , unsigned long end );

Returns void, so there's literally nothing coming back to you. No errors, no status, nothing. She does her thing and she's gone πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • start β€” where the range starts, bestie. The beginning. The alpha. The unsigned long in question πŸ’–
  • end β€” where the range ends. The finish line. Also an unsigned long, also important, don't skip her 🫢

πŸ’œ DESCRIPTION πŸ’œ

So here's the tea: KMSAN unmaps the metadata pages for the given range. And β€” this is the part where it's lowkey different from her cousin β€” unlike for vunmap_page_range, she also deallocates them. The way that's a whole extra step is giving main character energy, ngl. Not just unmapped, but freed. Both. She ate πŸ“


⭐ SEE ALSO ⭐

Kernel file ./include/linux/kmsan.h, plus the whole KMSAN friend group chat, and we're @-ing every single one of them, no cap:


πŸ’€ Heads up: this page lives under ./include/linux in the source tree β€” that's where you'll find her, iykyk.

Alright bestie, that's the whole page, and yes she's short, but she's iconic 🌈 This one comes from ./include/linux, dated October 2026, and that's the whole sign-off β€” mwah πŸ’–πŸ§šβ€β™€οΈπŸŒΈ

πŸ“¦ where this page comes from