encode_reco...al_state_7_0(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’Ύ NAME πŸ’Ύ

encode_recovery_journal_state_7_0 β€” bestie, this one encodes the state of a recovery journal. That's it, that's the whole job, and honestly? She does it flawlessly. πŸ‘‘

(fun fact: the page header up top is encode_reco...al_state_7_0(9), which is just the function name doing a little stretch β€” it lives in the Kernel API Manual πŸŽ€)


✨ SYNOPSIS ✨

void encode_recovery_journal_state_7_0 (u8 *buffer , size_t *offset ,
       struct recovery_journal_state_7_0 state );

Okay so look at her signature πŸ‘€ β€” she returns void, takes three things, and she's not here to argue with you about it. Slay.


🫢 ARGUMENTS 🫢

  • buffer β€” a buffer to store the encoding. Yes queen, that's where the encoded bytes go πŸ’–
  • offset β€” the offset in the buffer at which to encode. She starts writing right there, iykyk πŸ“
  • state β€” the recovery journal state to encode. That's the struct recovery_journal_state_7_0 in question, no cap 🌸

πŸ”₯ RETURN πŸ”₯

VDO_SUCCESS or an error code. That's the whole vibe check β€” either it ate or it didn't 😭


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/md/dm-vdo/encodings.c, plus this absolutely iconic lineup of friends (yes, the whole group chat showed up, don't skip anyone 🫢):


and that's the whole page bestie, go encode some journal state πŸ’…βœ¨

sign-off szn πŸŽ€ β€” this little masterpiece lives at ./drivers/md/dm-vdo and it's dated October 2026, page title encode_reco...al_state_7_0(9). mwah πŸ’‹

πŸ“¦ where this page comes from