xa_store_range(9)

💅 xa_store_range — like, the kernel API manual, but make it make sense

okay so bestie, we're in the Kernel API Manual today and the star of the show is xa_store_range(9). Buckle up. 🎀

---

✨ NAME ✨

xa_store_range — store this entry at a whole range of indices in the XArray. yeah. a range. not one index. a whole squad of them. 💅

---

🌸 SYNOPSIS 🌸

void * xa_store_range (struct xarray *xa , unsigned long first ,
       unsigned long last , void *entry , gfp_t gfp );

look at her. five arguments. she's doing the most and honestly? she ate. 🔥

---

🦋 ARGUMENTS 🦋

• xa — the XArray. that's the thing we're storing into, bestie, keep up 🫶
• first — the first index to affect. the beginning of the era, if you will.
• last — the last index to affect. the end of the era. it is inclusive, iykyk.
• entry — the new entry. the moment. the main character.
• gfp — memory allocation flags. basically the vibe check for how we're allowed to allocate memory 🌈

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — after this function returns, loads from any index between first and last, inclusive, will return entry. every single one. no cap. literally all of them. ✨

and if you store into an existing multi-index entry? it updates the entry of every index. the way that it just goes and updates all of them... iconic. 👑

one thing though — the marks associated with the index are unaffected, unless entry is NULL. so if you're passing NULL in there, bestie, the marks are catching strays. just so you know. 💀

---

🧚 CONTEXT 🧚

• Process context. 🫧
• It takes and releases the xa_lock. she's responsible like that.
• It may sleep if the gfp flags permit. so like... she can nap, but only if you said it was okay 😴

---

⭐ RETURN ⭐

• NULL on success 🎉
• xa_err(-EINVAL) if entry cannot be stored in an XArray 🙈
• xa_err(-ENOMEM) if memory allocation failed 😭

fr fr check your return value. don't just assume it slayed.

---

🍓 SEE ALSO 🍓

Kernel file ./lib/xarray.c, plus the whole friend group:

• xas_load(9), xas_nomem(9), xas_free_nodes(9), xas_create_range(9), xas_store(9), xas_get_mark(9), xas_set_mark(9), xas_clear_mark(9), xas_init_marks(9), xas_split_alloc(9), xas_split(9), xas_try_split_min_order(9), xas_try_split(9), xas_pause(9), xas_find(9), xas_find_marked(9), xas_find_conflict(9), xa_load(9), __xa_erase(9), xa_erase(9), __xa_store(9), xa_store(9), __xa_cmpxchg(9), __xa_insert(9), xas_get_order(9), xa_get_order(9), __xa_alloc(9), __xa_alloc_cyclic(9), __xa_set_mark(9), __xa_clear_mark(9), xa_get_mark(9), xa_set_mark(9), xa_clear_mark(9), xa_find(9), xa_find_after(9), xa_extract(9), xa_delete_node(9), xa_destroy(9)

like, the entire extended family showed up to the function. we love a supportive cast 🫶💜

---

and that's the whole page, bestie ✨ this one lives in ./lib and it's dated October 2026 — so yeah, go off, see you in the future 👋💅🎀