disk_set_ind...ccess_ranges(9)

💅 disk_set_ind...ccess_ranges(9) — from the Kernel API Manual, bestie ✨

okay so real talk, this is a function from the Kernel API Manual and it's about telling a disk which parts of it are, like, independently accessible. yes bestie, disks have ✨zones✨ now. let's get into it 🎀

---

🌸 NAME 🌸

disk_set_independent_access_ranges — set a disk's independent access ranges 💫

---

✨ SYNOPSIS ✨

void disk_set_independent_access_ranges (struct gendisk *disk , struct
blk_independent_access_ranges *iars );

like, that's the whole signature, no cap 🫶

---

🦋 ARGUMENTS 🦋

• disk — the target disk</> 🎯 you know, the one we're doing this to
• iars — the independent access ranges structure</> 👑 the actual data we're handing over

---

🍓 DESCRIPTION 🍓

So what this does: it sets the independent access ranges info on the request queue of disk to whatever iars is. icon behaviour, honestly 💅

now the ✨special cases✨, and pls pay attention because these matter:

• if iars is NULL, then the independent access ranges structure that's already set gets cleared. bye bestie 👋
• if there are no differences between iars and the independent access ranges structure that's already set, then iars gets freed 🫧 — like, thanks for nothing but also we're cleaning up after you

no notes, it's giving efficient 🌈

lowkey important: that last one means you don't get to keep using iars after this call if it was identical to what's already there. the function ate it. 💀

---

🔥 SEE ALSO 🔥

• Kernel file ./block/blk-ia-ranges.c — go read the source, iykyk 📖
• disk_register_independent_access_ranges(9) 💖
• disk_alloc_independent_access_ranges(9) 💖

---

🎀 the cute sign-off 🎀

this masterpiece lives in the ./block section of the kernel docs, and it was dated October 2026 — so yeah, it's from the future, slay ⭐👑

that's it, that's the page. go set some access ranges, main character 💜🧚