blk_flush_complete_seq(9)

🎀 blk_flush_complete_seq(9) 🎀

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function with a big job and she's literally the closer of the flush-sequence friend group 💅

---

💖 NAME 💖

blk_flush_complete_seq — complete the flush sequence. that's it, that's the whole vibe 🫶

---

✨ SYNOPSIS ✨

void blk_flush_complete_seq (struct request *rq , struct blk_flush_queue
*fq , unsigned int seq , blk_status_t error );

no cap, she returns void — no little gift back, just vibes and side effects 🌸

---

🦋 ARGUMENTS 🦋

• rq — the PREFLUSH/FUA request that's being sequenced. she's the main character here 👑
• fq — the flush queue. literally the group chat she lives in 💬
• seq — the sequences to complete, aka a mask of REQ_FSEQ_*. and yes, it can be zero — zero is a valid mask, we don't shame her 🙈
• error — whether an error occurred. a blk_status_t, so she's got range 😭

---

🌈 DESCRIPTION 🌈

so rq just completed the seq part of its flush sequence (slay 💅). this function records that completion and then triggers the next step — like, she logs the W and then hits "next" for the whole pipeline 🔥

---

🔒 CONTEXT 🔒

gets called with the spinlock held, specifically:

spin_lock_irq(fq->mq_flush_lock)

so yeah, you're already inside the lock bestie, don't go grabbing it again 😭 that's an own-goal fr fr

---

🌸 SEE ALSO 🌸

• the kernel file ./block/blk-flush.c — the source of truth, go read her 🍓
• blk_kick_flush(9) — her bestie who kicks things off ⭐
• blkdev_issue_flush(9) — the one who actually issues the flush 🧚

---

ok and one last thing — the lock in CONTEXT is not a suggestion, it's the whole assignment. hold it, do the work, carry on 💜

---

that's the page!! written up in ./block, dated October 2026, and she answers to the name blk_flush_complete_seq(9) — mwah, bye bestie 💖✨🎀