vdo_replay_...lab_journals(9)

💅 vdo_replay_into_slab_journals (9) — a Kernel API Manual moment

okay so bestie, this one lives in the Kernel API Manual, and the function is literally called vdo_replay_into_slab_journals (yes, the page header truncates it to vdo_replay_...lab_journals(9) 💀, that's just the header being dramatic and running out of room, not a different function). Buckle up, we're recovering journal entries 🎀

---

✨ NAME ✨

vdo_replay_into_slab_journals — replay recovery journal entries in the slab journals of slabs owned by a given block_allocator. That's the whole vibe: it replays, it goes into slab journals, it's scoped to one allocator's slabs. periodt 💅

---

🌸 SYNOPSIS 🌸

void vdo_replay_into_slab_journals (struct block_allocator *allocator ,
void *context );

two args, returns nothing, gets straight to business 🫶

---

🦋 ARGUMENTS 🦋

• allocator — the allocator whose slab journals are to be recovered. like, this is the one getting its journals replayed, no cap. 👑
• context — the slab depot load context supplied by a recovery when it loads the depot. it's the little care package the recovery hands over so this function knows what's up. 🎀

---

🔥 SEE ALSO 🔥

the whole friend group, and yes we're listing every single one — no skipping, iykyk 💖

• Kernel file ./drivers/md/dm-vdo/repair.c — that's the home base, the main character file ✨
• as_repair_completion(9)
• abort_repair(9)
• abort_on_error(9)
• drain_slab_depot(9)
• flush_block_map_updates(9)
• handle_page_load_error(9)
• unmap_entry(9)
• remove_out_of_bounds_entries(9)
• process_slot(9)
• rebuild_reference_counts_from_page(9)
• page_loaded(9)
• fetch_page(9)
• rebuild_from_leaves(9)
• process_entry(9)
• advance_points(9)
• before_recovery_point(9)
• get_entry(9)
• validate_recovery_journal_entry(9)
• add_slab_journal_entries(9)
• find_entry_starting_next_page(9)
• get_recovery_journal_block_header(9)
• is_valid_recovery_journal_block(9)
• is_exact_recovery_journal_block(9)
• find_recovery_journal_head_and_tail(9)
• unpack_entry(9)
• append_sector_entries(9)
• extract_new_mappings(9)
• compute_usages(9)
• vdo_repair(9)

all of them. every last one. that's the squad and they all ate 🍓

---

ngl bestie, this is kernel-side recovery code — read it carefully, don't go poking at it on a whim 🙈

---

and that's the whole page! mwah 💋 this one came from the Kernel API Manual, source path ./drivers/md/dm-vdo, dated October 2026 — and the footer still signs it vdo_replay_...lab_journals(9) because the header never got over it 💀🫶