before_recovery_point(9)

Okay so bestie, welcome to before_recovery_point(9) from the Kernel API Manual — it's giving tiny truth-checker energy and we're obsessed. 💖

🌸 NAME 🌸

before_recovery_point — check whether the first point precedes the second point. Lowkey iconic, periodt. 💅

✨ SYNOPSIS ✨

The whole signature is right here, no cap:

bool before_recovery_point (const struct recovery_point *first , const struct recovery_point *second );

🎀 ARGUMENTS 🎀

• first — the first recovery point. That's the main character of this little check, iykyk. 🫶
• second — the second recovery point. The other half of the vibe check. ✨

💖 RETURN 💖

It returns true if the first point precedes the second point. That's it, no cap — short, sweet, and iconic. 👑

🦋 SEE ALSO 🦋

The SEE ALSO section starts with the Kernel file ./drivers/md/dm-vdo/repair.c and then name-drops this entire friend group, in order. Ngl, it's a whole squad:

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

Cute sign-off: this page is from ./drivers/md/dm-vdo, dated October 2026, and its footer names before_recovery_point(9). Bye bestie, slay the recovery points! 💜