mmu_interval_read_retry(9)
π mmu_interval_read_retry(9) β like, the Kernel API Manual, bestie β¨
okay so welcome to the glow-up of mmu_interval_read_retry, straight out of the Kernel API Manual. she's a bool-returning icon and she's here to close out a read side critical section against a VA range. no cap, this one's important, so pay attention π
β¨ NAME β¨
mmu_interval_read_retry β bestie, this is how you end a read side critical section against a VA range. that's the whole vibe. π¦
πΈ SYNOPSIS πΈ
bool mmu_interval_read_retry (struct mmu_interval_notifier *interval_sub
, unsigned long seq );
π§ ARGUMENTS π§
interval_subβ the subscription. yes, THE subscription. she's the main character here πseqβ the return of the pairedmmu_interval_read_begin. like, you gotta bring back what her sister gave you, that's the whole deal π
π₯ DESCRIPTION π₯
okay so listen up, because this is a MUST: you have to call this under a user provided lock that is also held unconditionally by op->invalidate when it calls mmu_interval_set_seq. not optional. not "ehh probably fine". MUST. π
each call should be paired with a single mmu_interval_read_begin, and it should be used to conclude the read side. one begin, one retry-check, that's the ship dynamic π«Ά
β RETURN β
returns true if an invalidation collided with this critical section π β and that means the caller should retry. like, try again babe, the vibes were off the first time π
π SEE ALSO π
- Kernel file
./include/linux/mmu_notifier.h enum mmu_notifier_event(9)struct mmu_interval_notifier_finish(9)struct mmu_interval_notifier_ops(9)mmu_interval_set_seq(9)mmu_interval_check_retry(9)
these are literally the friend group, go read them too π
mwah π this page came to you from ./include/linux, stamped October 2026 β that's the source and the date, bestie, noted and slayed. periodt. β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms