find_recove...ead_and_tail(9)

🌸 NAME 🌸

okay so bestie, this is find_recovery_journal_head_and_tail — and what it does is literally Find the tail and head of the journal. that's the whole vibe 💅

---

✨ SYNOPSIS ✨

bool find_recovery_journal_head_and_tail (struct repair_completion
*repair );

yes she returns a bool, and yes the synopsis line is formatted exactly like that, no I will not be fixing it 💀

---

🫶 ARGUMENTS 🫶

• repair — the repair completion. that's it. that's the whole argument. she takes exactly one (1) thing and it's the repair completion 🔥

---

👑 RETURN 👑

returns True if there were valid journal blocks 💖 (and if there weren't... well. not True. you get it. iykyk 🌈)

---

🦋 SEE ALSO 🦋

the squad 💜 — all of these live in the kernel file ./drivers/md/dm-vdo/repair.c:

• 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)
• vdo_replay_into_slab_journals(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)
• unpack_entry(9)
• append_sector_entries(9)
• extract_new_mappings(9)
• compute_usages(9)
• vdo_repair(9)

like, that's the whole friend group, no cap 🎀

---

oh and real quick — the page title herself is find_recove...ead_and_tail(9) because she got truncated mid-name and honestly? iconic energy. she contains multitudes 💀✨

and that's the page!! mwah 💋 this one came to you straight from ./drivers/md/dm-vdo, version October 2026, in the Kernel API Manual — go forth and find those journal heads and tails bestie, you're gonna slay 🧚‍♀️💜