vdo_before_journal_point(9)

💖 vdo_before_journal_point(9) 💖

okay bestie, this one’s from the Kernel API Manual, and the whole assignment is a tiny vibe check: vdo_before_journal_point checks whether the first point precedes the second point. no cap, that’s the plot. 🎀

✨ NAME ✨

vdo_before_journal_point — Check whether the first point precedes the second point. literally. 💅

🦋 SYNOPSIS 🦋

bool vdo_before_journal_point (const struct journal_point *first , const
       struct journal_point *second );

🫶 ARGUMENTS 🫶

• first — The first journal point. main character energy, first in line. 💖
• second — The second journal point. the other half of the comparison, periodt. ✨

⭐ RETURN ⭐

Returns true if the first point precedes the second point. that’s the whole result, and honestly? iconic. 👑

🌈 SEE ALSO 🌈

Kernel file ./drivers/md/dm-vdo/encodings.h and Block map entries(9) — plus the whole friend group, all here so nobody gets left on read:

• vdo_are_same_version(9)
• vdo_pack_version_number(9)
• vdo_unpack_version_number(9)
• vdo_pack_header(9)
• vdo_unpack_header(9)
• vdo_get_index_region_start(9)
• vdo_get_data_region_start(9)
• vdo_get_index_region_size(9)
• vdo_pack_recovery_journal_entry(9)
• vdo_unpack_recovery_journal_entry(9)
• vdo_is_valid_recovery_journal_sector(9)
• vdo_compute_recovery_journal_block_number(9)
• vdo_get_journal_block_sector(9)
• vdo_pack_recovery_block_header(9)
• vdo_unpack_recovery_block_header(9)
• vdo_compute_slab_count(9)
• vdo_get_saved_reference_count_size(9)
• vdo_get_slab_journal_start_block(9)
• vdo_advance_journal_point(9)
• vdo_pack_journal_point(9)
• vdo_unpack_journal_point(9)
• vdo_pack_slab_journal_block_header(9)
• vdo_unpack_slab_journal_block_header(9)
• vdo_pack_slab_journal_entry(9)
• vdo_unpack_slab_journal_entry(9)
• vdo_get_slab_summary_hint_shift(9)

mwah 💋 that’s the page. source/version + date credit: ./drivers/md/dm-vdo • October 2026 • vdo_before_journal_point(9) 🫶🌸