scatterwalk_next(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ scatterwalk_next(9) ✨

okay so this is the scatterwalk_next(9) page from the Kernel API Manual β€” and yes, it's giving "tiny function, very important follow-up." 🫢

πŸ’– NAME πŸ’–

scatterwalk_next - Get the next data buffer in a scatterlist walk 🌈

πŸŽ€ SYNOPSIS πŸŽ€

unsigned int scatterwalk_next (struct scatter_walk *walk , unsigned int total );

πŸ‘€ ARGUMENTS πŸ‘€

  • walk β€” the scatter_walk ✨
  • total β€” the total number of bytes remaining, and bestie it has to be > 0 πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

A virtual address for the next segment of data from the scatterlist will be placed into walk->addr. That's the main character move here. πŸ‘‘

The caller must call scatterwalk_done_src or scatterwalk_done_dst when it is done using this virtual address. Not optional, no cap. 🚨

bestie, don't forget the done call β€” this is the "you break it, you fix it" part of the walk. πŸ’€

πŸ”₯ RETURN πŸ”₯

the next number of bytes available, <= total ⭐

🌸 SEE ALSO 🌸


and that's the whole vibe 🧚 β€” this page lives under ./include/crypto, dated October 2026, and it's literally scatterwalk_next(9). mwah πŸ’‹

πŸ“¦ where this page comes from