mmu_interval...ifier_remove(9)

💅 mmu_interval...ifier_remove(9) — from the Kernel API Manual, bestie ✨

Ok so listen. We're in the Kernel API Manual today and the star of the show is mmu_interval_notifier_remove(9) — yes the header truncates it, yes it's giving "my name didn't fit on the eyeliner pencil", but that's literally the name, no cap. 🎀

---

✨ NAME ✨

mmu_interval_notifier_remove — Remove a interval notifier 🧹

---

🌸 SYNOPSIS 🌸

void mmu_interval_notifier_remove (struct mmu_interval_notifier
*interval_sub );

---

🦋 ARGUMENTS 🦋

• interval_sub — the Interval subscription to unregister 🫶 Like, this is the thing you're yeeting out of the registry.

---

💖 DESCRIPTION 💖

Okay so this one has RULES, and the rules are not optional:

• This function must be paired with mmu_interval_notifier_insert. They're a matched set, an iconic duo, you don't get one without the other. 💫
• It cannot be called from any ops callback. Like, absolutely not. Don't even think about it. 🙈

And here's the payoff, the part that ate: once this returns, ops callbacks are no longer running on other CPUs and will not be called in future. Periodt. 💀✨ That's the whole vibe — you call it, and you know for a fact nobody's gonna slide into your callbacks afterwards.

---

👑 SEE ALSO 👑

Kernel file ./mm/mmu_notifier.c, plus the whole friend group:

• mmu_interval_read_begin(9)
• mmu_notifier_register(9)
• mmu_notifier_get_locked(9)
• mmu_notifier_put(9)
• mmu_interval_notifier_insert(9)
• mmu_notifier_synchronize(9)

---

Okay that's the page, go touch some kernel code, ily 🫶 💖

This little number lives in ./mm and it's stamped October 2026 — so yeah, it's from the future, main character energy fr fr. 💅⭐🌈