scatterwalk_done_dst(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ scatterwalk_done_dst(9) πŸŽ€

okay so bestie, you're looking at the Kernel API Manual page for scatterwalk_done_dst(9) β€” yes, we folded that manual-name moment right in, and honestly? iconic πŸ’….


🌸 NAME 🌸

scatterwalk_done_dst β€” finish one step of a walk of destination scatterlist. periodt ✨


✨ SYNOPSIS ✨

void scatterwalk_done_dst (struct scatter_walk *walk , unsigned int
       nbytes );

πŸŽ€ ARGUMENTS πŸŽ€

  • walk β€” the scatter_walk. literally the walk bestie 🫢
  • nbytes β€” the number of bytes processed this step, less than or equal to the number of bytes that scatterwalk_next returned. no cap, that β€œless than or equal to” part matters πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

Use this if the mapped address may have been written to, i.e. it is destination data. that's the vibe check: destination data, written-to possibility, use this one πŸ’…βœ¨


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./include/crypto/scatterwalk.h, plus these little friends:


source/version: ./include/crypto Β· date: October 2026 Β· page: scatterwalk_done_dst(9) β€” bye bestie, go finish that walk slay πŸ’–πŸ«Ά

πŸ“¦ where this page comes from