validate_completed_page(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… validate_completed_page(9) πŸ’…

okay bestie, welcome to the Kernel API Manual page for validate_completed_page(9). This is the little sanity check for a page completion that's being freed to the cache: it checks that the completion referred to a valid page and that the page is in a valid state. No cap, that's the whole assignment. 🫢

πŸŽ€ NAME πŸŽ€

validate_completed_page β€” check that a page completion which is being freed to the cache referred to a valid page and is in a valid state. It's giving "validity check before it goes back to the cache" energy. πŸ’–

✨ SYNOPSIS ✨

int validate_completed_page (struct vdo_page_completion *completion ,
bool writable );

πŸ’… ARGUMENTS πŸ’…

  • completion β€” the page completion to check. It's the struct vdo_page_completion * under inspection, bestie. πŸ”
  • writable β€” whether a writable page is required. It's a bool, so yes/no, writable or not, periodt. πŸ¦‹

πŸ”₯ RETURN πŸ”₯

VDO_SUCCESS if the page was valid, otherwise as error. So valid page? You get VDO_SUCCESS. Not valid? It's giving error instead. That's the return tea. πŸ“

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/md/dm-vdo/block-map.c β€” and the whole block-map friend group is here too:


Cute sign-off: this page comes from source/version ./drivers/md/dm-vdo, dated October 2026. Stay valid, bestie πŸ’œβœ¨

πŸ“¦ where this page comes from