blk_rq_integ...ap_iter_next(9)

💅 blk_rq_integ...ap_iter_next(9) 💅

okay bestie, welcome to the Kernel API Manual ✨ this one's a tiny little function page but it's lowkey important, so let's get into it 🫶

---

✨ NAME ✨

blk_rq_integrity_dma_map_iter_next — maps the next integrity DMA segment for a request 🎀

---

🌸 SYNOPSIS 🌸

bool blk_rq_integrity_dma_map_iter_next (struct request *req , struct
       device *dma_dev , struct blk_dma_iter *iter );

that's the whole signature, no cap 💅 it returns a bool, so it's a yes/no girlie at heart.

---

🦋 ARGUMENTS 🦋

• req — the request you wanna map, that's the main character here 👑
• dma_dev — the device you're mapping to 🎯
• iter — the block layer DMA iterator, your little state-tracking bestie 🌈

---

💖 DESCRIPTION 💖

so here's the vibe: you call this to iterate to the next integrity mapping, right after a previous call to blk_rq_integrity_dma_map_iter_start. like, you already started the journey, this is you taking the next step 🧚✨ and if you want the full tea on what the arguments actually mean, go read the description over at blk_rq_integrity_dma_map_iter_start — it's all there, iykyk.

it returns false if there's no segment to map — and yes, that includes when something errored out 😭 — or true if it actually did map a segment. slay 💅

and if a segment was mapped: the DMA address for it comes back in iter.addr and the length in iter.len 🎀 if no segment was mapped, the status code comes back in iter.status instead. so either way you're getting info, she always delivers 💜

---

🔥 SEE ALSO 🔥

• Kernel file ./block/blk-mq-dma.c
• blk_rq_dma_map_iter_start(9)
• blk_rq_dma_map_iter_next(9)
• blk_rq_integrity_dma_map_iter_start(9)
• blk_rq_map_integrity_sg(9)

go read those next, bestie, they're literally the whole friend group 🌸

---

ngl this page is short but she ate. no notes. 💅

---

okay that's the whole page!! 🎀 this cutie lives in ./block and the version/date stamp on her is October 2026 — mwah, see you in the next manpage, bestie 💖✨🦋