add_queued_recovery_entries(9)

💅 add_queued_recovery_entries — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for add_queued_recovery_entries(9). this is a little corner of the dm-vdo universe and we're gonna get you comfy with it, no cap ✨

---

🎀 NAME

add_queued_recovery_entries — the function that actually adds entries from the queue to the given block. like, the queue has been sitting there holding its little entries and this is the moment they get officially moved in. it's giving "moving day" energy 🚚💖

---

✨ SYNOPSIS

void add_queued_recovery_entries (struct recovery_journal_block *block
      );

one argument, returns nothing — it's void, so don't go looking for a return value, she doesn't do that 👑 (the whole signature is literally one line, keep it exactly as-is!)

---

🫶 ARGUMENTS

• block — the journal block. that's it, that's the whole vibe. it's a struct recovery_journal_block * and yes, the journal block is the main character here 🦋

---

🌈 SEE ALSO

okay this is the group chat of related pages and we are NOT leaving anyone out, everybody gets an invite 💌 (and yeah, the kernel file itself is in there too):

• Kernel file ./drivers/md/dm-vdo/recovery-journal.c, Lock Counters.(9), get_zone_count_ptr(9), get_counter(9), is_journal_zone_locked(9)
• vdo_release_recovery_journal_block_reference(9), pop_free_list(9), is_block_dirty(9), is_block_empty(9), is_block_full(9), assert_on_journal_thread(9)
• continue_waiter(9), has_block_waiters(9), suspend_lock_counter(9), check_for_drain_complete(9)
• notify_recovery_journal_of_read_only_mode(9), enter_journal_read_only_mode(9)
• vdo_get_recovery_journal_current_sequence_number(9), get_recovery_journal_head(9), compute_recovery_count_byte(9)
• check_slab_journal_commit_threshold(9), finish_reaping(9), complete_reaping(9), handle_flush_error(9)
• initialize_journal_state(9), vdo_get_recovery_journal_length(9), reap_recovery_journal_callback(9)
• initialize_lock_counter(9), set_journal_tail(9), initialize_recovery_block(9)
• vdo_decode_recovery_journal(9), vdo_free_recovery_journal(9), vdo_initialize_recovery_journal_post_repair(9)
• vdo_get_journal_block_map_data_blocks_used(9), vdo_get_recovery_journal_thread_id(9), vdo_open_recovery_journal(9), vdo_record_recovery_journal(9)
• get_block_header(9), set_active_sector(9), advance_tail(9), initialize_lock_count(9)
• prepare_to_assign_entry(9), schedule_block_write(9), release_journal_block_reference(9), assign_entry(9)
• recycle_journal_block(9), continue_committed_waiter(9), notify_commit_waiters(9), recycle_journal_blocks(9)
• complete_write(9), write_block(9), write_blocks(9), vdo_add_recovery_journal_entry(9)
• is_lock_locked(9), reap_recovery_journal(9), vdo_acquire_recovery_journal_block_reference(9)
• vdo_release_journal_entry_lock(9), vdo_drain_recovery_journal(9), resume_lock_counter(9), vdo_resume_recovery_journal(9)
• vdo_get_recovery_journal_logical_blocks_used(9), vdo_get_recovery_journal_statistics(9), dump_recovery_block(9), vdo_dump_recovery_journal_statistics(9)

---

ngl bestie, if you're deep in the recovery journal, this little function is lowkey the one that makes the handoff happen. go read the whole squad above, iykyk 💅

okay that's the page!! mwah 🫶 this iconic little doc lives over in ./drivers/md/dm-vdo, stamped October 2026, and it's forever known as add_queued_recovery_entries(9) — periodt 🌸💜