bio_advance(9)

💅 bio_advance — Kernel API Manual ✨

okay bestie, so you're in the kernel docs, section 9, and the star of the show is bio_advance. no cap, this one's a little workhorse and she eats every time 🫶

---

🌸 NAME 🌸

bio_advance — increment/complete a bio by some number of bytes 💫

---

🎀 SYNOPSIS 🎀

void bio_advance (struct bio *bio , unsigned int nbytes );

literally just two args and she returns void. lowkey iconic. 👑

---

🦋 ARGUMENTS 🦋

• bio — the bio you wanna advance, bestie. that's the one getting moved along.
• nbytes — the number of bytes to complete. how far forward we're pushing it. 📏

---

✨ DESCRIPTION ✨

so here's the vibe check 👀 — this updates bi_sector, bi_size and bi_idx.

and like, if the number of bytes you're completing doesn't align with a bvec boundary? then bv_len and bv_offset will get updated on the last bvec as well. yeah, she does the fiddly edge-case work too, no complaints. 💅

after that, bio will then represent the remaining, uncompleted portion of the io. so it's giving "what's left" energy, fr fr. 🧚

---

🌈 SEE ALSO 🌈

the kernel file ./include/linux/bio.h plus the whole friend group:

• struct folio_iter(9)
• bio_for_each_folio_all(9)
• bio_next_split(9)
• bio_in_atomic(9)
• bio_complete_in_task(9)
• bio_endio_status(9)
• bio_iov_bounce_nr_vecs(9)
• bio_add_max_vecs(9)
• bio_is_zone_append(9)

go say hi, they all live in ./include/linux and they're all super friendly. 💖

---

ngl bestie, keep those bi_sector, bi_size, bi_idx, bv_len and bv_offset updates in mind — those are the exact fields she touches. no invented behaviour here, just what the page says. 🙈

---

⭐ that's a wrap! this page comes to you from ./include/linux, dated October 2026, and it's bio_advance(9) all the way down. mwah, go read your bios 💋🎀