assign_entry(9)
π assign_entry(9) π
okay so bestie, welcome to the Kernel API Manual page for assign_entry β yes it's a man page, yes it's section 9, and yes we're gonna get through it together, it's literally so short you'll be done before your iced coffee melts π§β¨
πΈ NAME πΈ
assign_entry β assign an entry waiter to the active block.
That's it. That's the whole name section. Iconic minimalism, no notes π
π¦ SYNOPSIS π¦
void assign_entry (struct vdo_waiter *waiter , void *context );
copy it exactly like that, spaces around the commas and all, don't @ me, the man page said so π«Ά
β¨ ARGUMENTS β¨
waiterβ thedata_vio. that's your waiter right there, main character of the call πcontextβ the recovery journal block. that's the block the waiter is getting handed off to.
two args. two. we love a low-effort signature ngl π€
π DESCRIPTION π
so what does it actually do? it implements waiter_callback_fn. that's the whole description, fr fr β it's a callback function, and this page is just here to tell you that π§
like... that's genuinely all the manual gives us. no lore, no backstory, just "implements waiter_callback_fn" and a dip π respect the mystery honestly.
bestie I'm not gonna make up extra behaviour for you β the page doesn't say more, so neither do I. the source file is right there if you want the real tea π
π SEE ALSO π
bestie. BESTIE. buckle up. this list is long, and every single one of these is real and has to be here, so let's gooo π₯
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)recycle_journal_block(9)continue_committed_waiter(9)notify_commit_waiters(9)recycle_journal_blocks(9)complete_write(9)add_queued_recovery_entries(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)
sixty-three entries. SIXTY-THREE. the way this page said "here's two lines of description and also an entire syllabus" ππ slay though, we got through it π«Ά
that's the whole page, bestie β love that for us β¨ this cutie lives in ./drivers/md/dm-vdo, it's dated October 2026, and it's filed under assign_entry(9). mwah, go read the source, ily, bye πππ¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms