extract_new_mappings(9)

💅 extract_new_mappings(9) — Kernel API Manual energy

Okay bestie, welcome to the extract_new_mappings page, straight out of the Kernel API Manual 🎀. It's a whole function, it takes one arg, and it's lowkey doing the lord's work in the VDO repair code. Let's get into it ✨

---

✨ NAME ✨

extract_new_mappings — finds, like, all the valid new mappings that are gonna get applied to the block map. That's the whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

int extract_new_mappings (struct repair_completion *repair );

Yeah. That's it. One parameter, returns an int. Iconic minimalism. 💅

---

🎀 ARGUMENTS 🎀

• repair — the repair completion. That's your one (1) input, bestie. <italic>repair</italic> is literally the entire personality of this function call. 🫶

---

👑 DESCRIPTION 👑

So here's the tea ☕: the mappings get extracted from the journal and then stored in a sortable array. Why tho? Because that way, all of the mappings that need to be applied to a given block map page can be done in a single page fetch. One fetch. One trip. No redundant page-pulling nonsense. Efficiency ate. 🔥

That's the whole strategy — pull 'em out, sort 'em nice, then hit each block map page exactly once. Main character energy from the journal, honestly. 🌈

---

⭐ SEE ALSO ⭐

All these fellow icons live in the kernel file ./drivers/md/dm-vdo/repair.c — go say hi 🧚:

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

---

Fr fr, that's the entire posse. No cap, go read them all if you wanna understand the repair pipeline end to end 💀

---

And that's the page, bestie! 💖 Source path: ./drivers/md/dm-vdo, dated October 2026 — extract_new_mappings(9), slaying in a kernel near you. Periodt. 👑✨