process_entry(9)

💖 NAME 💖

Hey bestie 💖 welcome to process_entry(9), a page straight outta the Kernel API Manual. This one is all about processing a single entry from the block map tree. ✨

✨ SYNOPSIS ✨

int process_entry (physical_block_number_t pbn , struct vdo_completion *completion );

🌸 ARGUMENTS 🌸

• pbn — A pbn which holds a block map tree page. That's the whole job, no cap. 🦋
• completion — The parent completion of the traversal, periodt. 💅

🦋 DESCRIPTION 🦋

Okay so this function implements vdo_entry_callback_fn. That's the vibe. It's giving callback implementation energy, and honestly? Iconic. ✨

🎀 RETURN 🎀

It returns VDO_SUCCESS or an error. Slay if it's VDO_SUCCESS 👑, and 😭 if it's an error.

💅 SEE ALSO 💅

Peep the related lore, bestie. The kernel file is ./drivers/md/dm-vdo/repair.c, and these pages are all linked up:

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

Catch ya later, bestie 🫶 — this is process_entry(9), source/version ./drivers/md/dm-vdo, dated October 2026. 💖✨