get_entry(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… get_entry(9) β€” main character energy πŸ’…

okay bestie, welcome to the Kernel API Manual corner where today's main character is get_entry(9). The whole plot is simple and lowkey iconic: we unpack the recovery journal entry that matches a given recovery point. No cap. πŸ’–


✨ NAME ✨

get_entry β€” unpack the recovery journal entry associated with the given recovery point. That's the vibe: you bring the recovery point, it brings back the matching entry, unpacked, slay. πŸ’…


🌸 SYNOPSIS 🌸

Here's the signature in all its glory, bestie β€” copy it exactly, no improvising:

struct recovery_journal_entry get_entry (const struct repair_completion
       *repair , const struct recovery_point *point );

πŸŽ€ ARGUMENTS πŸŽ€

  • repair β€” the repair completion. It's the const struct repair_completion * bestie coming through the door. 🫢
  • point β€” the recovery point. Also const struct recovery_point *, and yes she's the one we're matching. ✨

πŸ’– RETURN πŸ’–

The unpacked contents of the matching recovery journal entry. No mystery, no side quest: matching entry in, unpacked contents out. Periodt. πŸ’…


🌈 SEE ALSO 🌈

bestie, the whole squad of related pages lives in the kernel file ./drivers/md/dm-vdo/repair.c β€” here's the full roll call, no cap:


🫢 cute sign-off, bestie: source/version flex is ./drivers/md/dm-vdo, the date is October 2026, and this manual page is get_entry(9). That's the whole page β€” bye! πŸ’œ
πŸ“¦ where this page comes from