submit_bio_noacct(9)

✨ NAME ✨

submit_bio_noacct — re-submit a bio to the block device layer for I/O 💖

Hiii bestie, welcome to submit_bio_noacct(9) from the Kernel API Manual 🫶 This is the page where the block layer gets its little resubmit moment, and yes, it's very specific.

---

🌸 SYNOPSIS 🌸

void submit_bio_noacct (struct bio *bio );

---

🎀 ARGUMENTS 🎀

• bio — the bio that describes the location in memory and on the device 💅 Like, it's giving "here's where the data lives and here's where it's going," all in one struct.

---

🦋 DESCRIPTION 🦋

Okay so this is a version of submit_bio that shall only be used for I/O that is resubmitted to lower level drivers by stacking block drivers. No cap, that's the whole lane it stays in. It's not the general-purpose one, bestie.

All file systems and other upper level users of the block layer should use submit_bio instead. Periodt. If you're upper level, you want submit_bio; this one is for the stacking-driver girlies 🧚

Bestie warning: do not just vibe-check this into every I/O path. It has a very specific job, and the manual is clear about who should use submit_bio instead.

---

🌈 SEE ALSO 🌈

Kernel file ./block/blk-core.c — and the whole iconic squad:

• blk_queue_flag_set(9)
• blk_queue_flag_clear(9)
• blk_op_str(9)
• blk_sync_queue(9)
• blk_set_pm_only(9)
• blk_put_queue(9)
• blk_queue_enter(9)
• blk_get_queue(9)
• submit_bio(9)
• bio_poll(9)
• bio_start_io_acct(9)
• blk_lld_busy(9)
• blk_start_plug(9)
• blk_finish_plug(9)

---

💜 Cute lil sign-off: this page's footer energy is source/version ./block, dated October 2026. That's the whole vibe check, bestie — go forth and resubmit responsibly ✨🎀