xas_for_each_conflict(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ xas_for_each_conflict(9) β€” Kernel API Manual πŸ¦‹

okay bestie, welcome to xas_for_each_conflict(9) from the Kernel API Manual β€” this one is literally about looping over a range of an XArray, and it's giving β€œI know exactly which entries conflict” energy πŸ’…βœ¨

✨ NAME ✨

xas_for_each_conflict β€” iterate over a range of an XArray. fr fr, that's the whole vibe πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

xas_for_each_conflict (xas , entry );

the signature is right here, no cap: πŸ‘‘

🌸 ARGUMENTS 🌸

  • xas β€” XArray operation state. Like, the current state of your XArray operation, bestie.
  • entry β€” Entry retrieved from the array. The entry you just pulled out of the array.

πŸ’œ DESCRIPTION πŸ’œ

So here's the tea: the loop body will be executed for each entry in the XArray that lies within the range specified by xas. periodt.

If the loop terminates normally, entry will be NULL. iconic behavior.

The user may break out of the loop, which will leave entry set to the conflicting entry. not me pointing at the conflict like πŸ‘€

The caller may also call xa_set_err to exit the loop while setting an error to record the reason. slay, now the reason is documented. 🫢

🌈 SEE ALSO 🌈

Kernel file ./include/linux/xarray.h β€” plus the whole XArray friend group:


source check: ./include/linux, October 2026 β€” xas_for_each_conflict(9) is signing off from the Kernel API Manual πŸ«ΆπŸ’–βœ¨

πŸ“¦ where this page comes from