vdo_attempt_...ay_into_slab(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Okay so this is the vdo_attempt_replay_into_slab(9) page from the Kernel API Manual, and the whole assignment is: vdo_attempt_replay_into_slab β€” replay a recovery journal entry into a slab's journal. That's the vibe. πŸ‘‘


🌸 SYNOPSIS 🌸

Bestie, here's the exact signature, no cap:

bool vdo_attempt_replay_into_slab (struct vdo_slab *slab ,
physical_block_number_t pbn , enum journal_operation operation , bool
increment , struct journal_point *recovery_point , struct vdo_completion
*parent );

πŸŽ€ ARGUMENTS πŸŽ€

  • slab β€” the slab to play into. πŸ’…
  • pbn β€” the PBN for the entry. ✨
  • operation β€” the type of entry to add. πŸ¦‹
  • increment β€” True if this entry is an increment. πŸ”₯
  • recovery_point β€” the recovery journal point corresponding to this entry. 🌸
  • parent β€” the completion to notify when there is space to add the entry if the entry could not be added immediately. 🫢

πŸ’« RETURN πŸ’«

True if the entry was added immediately. That's the little bool tea. β˜•


🌈 SEE ALSO 🌈

All the linked girlies live around the kernel file ./drivers/md/dm-vdo/slab-depot.c:


This page is from source/version ./drivers/md/dm-vdo, dated October 2026 β€” mwah, bye bestie! πŸ’‹

πŸ“¦ where this page comes from