spu_no_incr_hash(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… spu_no_incr_hash(9) β€” from the Kernel API Manual bestie

okay so this is a kernel function, and honestly? it's giving "one job, does it well" energy. it lives in the kernel API manual and it's here to answer exactly one question: is incremental hashing supported or not. that's it. that's the whole vibe. πŸŽ€


🌸 NAME 🌸

spu_no_incr_hash β€” literally just tells you whether incremental hashing is supported. that's the assignment and it understood it. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

bool spu_no_incr_hash (struct iproc_ctx_s *ctx );

πŸ’– ARGUMENTS πŸ’–

  • ctx β€” the crypto session context 🫢 that's it, that's the only thing you pass in.

✨ DESCRIPTION ✨

so here's the tea, bestie: SPU-2 does not support incremental hashing. nope, not a thing, not happening. 😭 and the manpage is very honest about it β€” there's a whole note saying we'll have to revisit this and condition on chip revision or device tree entry if future versions do support incremental hash. so like… watch this space, iykyk. πŸ‘€

also SPU-M doesn't support incremental hashing of AES-XCBC. not that either. sorry babes. πŸ’€


πŸ‘‘ RETURN πŸ‘‘

  • true β€” incremental hashing is not supported πŸ™ˆ
  • false β€” otherwise

mind the double negative, bestie, it's literally the entire point of the function name. true means "no incr hash", periodt. ✨


πŸ”₯ SEE ALSO πŸ”₯

the kernel file you wanna peek at is ./drivers/crypto/bcm/cipher.c β€” and here's the whole friend group, all in one go:


ngl this one's a short read, but it's iconic in its own lowkey way. go read the whole squad up there if you want the full picture. πŸ’…

and that's a wrap, bestie!! this page came from ./drivers/crypto/bcm, dated October 2026 β€” mwah, slay, go call spu_no_incr_hash(9) responsibly πŸŒˆβ­πŸ’œ

πŸ“¦ where this page comes from