STRUCT MMU_INTERVAL_NOTIFIER_FINISH(9)

✨ struct mmu_...ifier_finish(9) ✨

okay so bestie, this is a page straight out of the Kernel API Manual, and it's giving “mmu_interval_notifier two-pass abstraction” realness 🫶 buckle up, it's lowkey important 👑

---

🌸 NAME 🌸

struct mmu_interval_notifier_finish — the mmu_interval_notifier two-pass abstraction, no cap 💅

---

🦋 SYNOPSIS 🦋

struct mmu_interval_notifier_finish {
    struct llist_node link;
    struct mmu_interval_notifier *notifier;
};

---

🎀 Members 🎀

• link — Lockless list link for the notifiers pending pass list 🔗
• notifier — The mmu_interval_notifier for which the finish pass is called ✨

---

💅 Description 💅

Allocate this thing, typically using GFP_NOWAIT, in the interval notifier's start pass. But listen: with a large number of notifiers implementing two passes, allocation with GFP_NOWAIT will become increasingly likely to fail 😭 so consider implementing a small pool instead of using kmalloc allocations. fr fr, plan ahead 🧚

If the implementation needs to pass data between the start and the finish passes, the recommended way is to embed struct mmu_interval_notifier_finish into a larger structure that also contains the data needed to be shared. Keep in mind that a notifier callback can be invoked in parallel, and each invocation needs its own struct mmu_interval_notifier_finish 👀

If allocation fails, then the mmu_interval_notifier_ops->invalidate_start op needs to implements the full notifier functionality. Please refer to its documentation. 💀

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/mmu_notifier.h — go check these besties:

• enum mmu_notifier_event(9)
• struct mmu_interval_notifier_ops(9)
• mmu_interval_set_seq(9)
• mmu_interval_read_retry(9)
• mmu_interval_check_retry(9)

---

xoxo, this page comes from ./include/linux, dated October 2026, and it's the struct mmu_...ifier_finish(9) manual page. periodt 💖🎀