dax_fault_iter(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dax_fault_iter β€” the Kernel API Manual, bestie edition πŸŽ€

okay so real talk, this page is from the Kernel API Manual (section 9, the kernel-functions girlies) and it's about one little function that does a very specific job. Let me put you on.


✨ NAME ✨

dax_fault_iter β€” the common actor that handles pfn insertion in a PTE/PMD fault. yes, that's the whole vibe. it's the shared worker bee that shows up to slot your pfn in, whether you're faulting at the PTE level or the PMD level πŸ’…


🌸 SYNOPSIS 🌸

vm_fault_t dax_fault_iter (struct vm_fault *vmf , const struct
       iomap_iter *iter , unsigned long *pfnp , struct xa_state *xas , void
       **entry , bool pmd );

it literally returns a vm_fault_t, no cap. take the args, do the thing, hand back your fault status 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

six args, she's thorough, we respect it:

  • vmf β€” your vm fault instance. the whole situation you're here to handle, iconic.
  • iter β€” the iomap iter. lowkey essential, it's the iteration context you're working inside.
  • pfnp β€” the pfn that's gonna be returned. it's a pointer, so yes, she writes back. main character energy for real πŸ”₯
  • xas β€” the dax mapping tree of a file. that's your struct xa_state, the map you're navigating 🌈
  • entry β€” an unlocked dax entry that's going to be inserted. unlocked is the key word here, don't forget it πŸ’€
  • pmd β€” the bool that tells you whether this is a pmd fault or not. PTE vs PMD, she's distinguishing, periodt πŸ‘‘
every argument matters, bestie β€” don't be out here passing the wrong one and then acting surprised 😭

πŸ‘‘ SEE ALSO πŸ‘‘

sibling functions, all from the kernel file ./fs/dax.c β€” go say hi, they're family:


and that's the page, bestie! πŸ’– sourcing this straight from ./fs, dated October 2026 β€” so go forth, insert your pfns responsibly, and slay βœ¨πŸ§šπŸ“

πŸ“¦ where this page comes from