has_block_waiters(9)

👑 has_block_waiters(9) — Kernel API Manual 💅

okay so bestie, welcome to the Kernel API Manual page for has_block_waiters, and no cap, this one is short, sweet, and lowkey iconic. it's giving "tiny function, big feelings" energy. let's get into it 🎀

---

✨ NAME ✨

has_block_waiters — check whether the journal has any waiters on any blocks. that's it. that's the whole vibe check 🦋

---

🌸 SYNOPSIS 🌸

bool has_block_waiters (struct recovery_journal *journal );

literally one function, one argument, returns a bool. main character energy, zero drama. ⭐

---

🫶 ARGUMENTS 🫶

• journal — the journal in question. yeah, that one. the journal we're snooping on. 👀

---

💖 RETURN 💖

Returns True if any block has a waiter. like, if even one block is out here waiting, you get True. not a single waiter? then it's not True, bestie, that's just how it goes. 🔥

---

🌈 SEE ALSO 🌈

okay this is the part where the manpage goes absolutely feral with the cross-references, and honestly? we love that for it. every single one, no skipping, because the one rule is keep every detail 🧚

• 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)
• 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)
• 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)

bestie that list is long. iykyk. if you're reading all of these in one sitting, drink some water and stretch, fr fr 💜

---

and that's the whole page, periodt. signing off from ./drivers/md/dm-vdo, dated October 2026, on the has_block_waiters(9) page — slay, go check your waiters, ily, bye! 💅✨🍓