scatterwalk_next(9)
β¨ 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β thescatter_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 πΈ
- Kernel file
./include/crypto/scatterwalk.hβ plus go say hi toscatterwalk_done_src(9)andscatterwalk_done_dst(9)π
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms