is_exact_re...ournal_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… is_exact_re...ournal_block(9) β€” like, the Kernel API Manual, but make it make sense πŸŽ€

okay bestie, so this little icon lives in the Kernel API Manual and its whole personality is "does this block match the exact one we're looking for?" β€” that's it, that's the vibe. no cap. ✨


🌸 NAME 🌸

is_exact_recovery_journal_block β€” determine whether the given header describes the exact block indicated. literally just a yes/no girlie. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

bool is_exact_recovery_journal_block (const struct recovery_journal
*journal , const struct recovery_block_header *header ,
sequence_number_t sequence );

πŸŽ€ ARGUMENTS πŸŽ€

  • journal β€” the journal to use. like, the main character of this whole situation. πŸ‘‘
  • header β€” the unpacked block header to check. she's giving "please verify me" energy. πŸ”₯
  • sequence β€” the expected sequence number. the number we're manifesting. ⭐

πŸ’œ RETURN πŸ’œ

True if the block matches. that's the whole answer. slay. βœ…


🌈 SEE ALSO 🌈

it's all hanging out in the kernel file ./drivers/md/dm-vdo/repair.c, bestie β€” here's the whole group chat:


πŸ’€ reminder: this is a kernel API page, so those (9) bits mean manual section 9, not "9 out of 10, would recommend". iykyk.

and that's the whole page, periodt. source/version: ./drivers/md/dm-vdo, dated October 2026 β€” catch you in the next manpage, bestie πŸ’…πŸ«ΆπŸŒΈ

πŸ“¦ where this page comes from