zfcp_qdio_fill_next(9)

✨ zfcp_qdio_fill_next ✨

okay bestie, welcome to the kernel API manual 💅 this one lives at zfcp_qdio_fill_next(9) and it's a tiny little function with a very specific job. Let's get into it 🫶

🌸 NAME 🌸

zfcp_qdio_fill_next — fill the next sbale, but like… only for single sbal requests. that's the whole vibe. ✨

🦋 SYNOPSIS 🦋

void zfcp_qdio_fill_next (struct zfcp_qdio *qdio , struct zfcp_qdio_req
*q_req , void *data , u32 len );

🎀 ARGUMENTS 🎀

• qdio — pointer to struct zfcp_qdio. yes. the whole qdio situation. 👑
• q_req — pointer to struct zfcp_queue_req. the request bestie in question 🫶
• data — pointer to data. that's the payload, the stuff, the actual content 💖
• len — length of data. how much of it there is, in numbers 🔢

💜 DESCRIPTION 💜

so here's the lore: this is only required for single sbal requests. that's it. that's the use case. 🎯

and listen — calling it when you're wrapping around to the next sbal is a bug. not a quirky little oopsie, an actual bug. so don't do that, bestie 😭 fr fr it's giving "undefined behaviour energy" and we are NOT here for it 💀

🚨 vibe check / warning: single sbal requests only. wrap-around calls = bug. periodt.

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/s390/scsi/zfcp_qdio.h and its whole friend group — go read them, they're iconic:

• struct zfcp_qdio(9)
• struct zfcp_qdio_req(9)
• zfcp_qdio_sbale_req(9)
• zfcp_qdio_sbale_curr(9)
• zfcp_qdio_req_init(9)
• zfcp_qdio_set_sbale_last(9)
• zfcp_qdio_skip_to_last_sbale(9)
• zfcp_qdio_sbal_limit(9)
• zfcp_qdio_set_data_div(9)
• zfcp_qdio_real_bytes(9)
• zfcp_qdio_set_scount(9)

---

that's the whole page, bestie — no notes, ate and left no crumbs 🍓

sign-off: this lil beauty comes from ./drivers/s390/scsi and it's dated October 2026. screenshot it, memorise it, tell your friends 💅🎀💖