mmu_notifier_synchronize(9)

✨ NAME ✨

okay so this is a page from the Kernel API Manual, and the main character is mmu_notifier_synchronize — its whole job is to ensure all mmu_notifiers are freed. no cap 💅

🦋 SYNOPSIS 🦋

void mmu_notifier_synchronize (void );

🎀 ARGUMENTS 🎀

• void — no arguments. literally zero. not a single one. 💀

🌸 DESCRIPTION 🌸

bestie, this function makes sure that all outstanding async SRU work from mmu_notifier_put is completed. like, it waits for the async stuff to finish before it lets you move on. periodt. ✨

After it returns, any mmu_notifier_ops associated with an unused mmu_notifier will no longer be called. so once this comes back, those ops are donezo — not getting called again. 🙈

Before using it, the caller must ensure that all of its mmu_notifiers have been fully released via mmu_notifier_put. that part is on you, bestie — do the release first, then call this. 🫶

Modules using the mmu_notifier_put API should call this in their __exit function to avoid module unloading races. so yeah, if you're a module with __exit, this is your girl. don't skip her, or the unloading races will absolutely come for you. 😭

race check: this is specifically about avoiding module unloading races, so __exit is the vibe. 🔥

👑 SEE ALSO 👑

• the kernel file ./mm/mmu_notifier.c
• mmu_interval_read_begin(9)
• mmu_notifier_register(9)
• mmu_notifier_get_locked(9)
• mmu_notifier_put(9)
• mmu_interval_notifier_insert(9)
• mmu_interval_notifier_remove(9)

okay bye bestie 💖 this little icon came from source/version ./mm, dated October 2026, and the page is mmu_notifier_synchronize(9) — slay and stay race-free 🌈