notify_commit_waiters(9)
πΈ notify_commit_waiters β bestie, your VIOs are UP π
okay so this is a page from the Kernel API Manual, section 9 β and it's about notify_commit_waiters, a function that's lowkey just doing its little job of telling everybody whose stuff finally landed. Let's get into it β¨
β¨ NAME β¨
notify_commit_waiters β Notify any VIOs whose entries have now committed.
like literally that's it. that's the whole vibe. someone's entries committed, and this function is the one going around being like "hey bestie, you're up" π«Ά
π SYNOPSIS π
void notify_commit_waiters (struct recovery_journal *journal );
it returns void, so don't be sitting there waiting for a return value, because there isn't one. it just does the thing. periodt.
π ARGUMENTS π
journalβ The recovery journal to update. yes queen, hand it over, it's the one getting updated π
π¦ SEE ALSO π¦
okay so this section is long β and I mean iconic-long, main-character-long, the way that it just keeps going. but every single one of these is part of the fam so we're listing all of them, no cap, no skipping π₯
Kernel file ./drivers/md/dm-vdo/recovery-journal.cLock 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)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-four entries. sixty-four!! we ate and left absolutely no crumbs π
π a lil sign-off π
that's the whole page, bestie π it lives over in ./drivers/md/dm-vdo, and this version is dated October 2026 β so like, very much current, no dusty manpage energy here. go forth and notify those waiters πβ¨π¦
π¦ 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