s5p_hash_final(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– s5p_hash_final(9) β€” Kernel API Manual πŸ’–

okay so bestie, welcome to the Kernel API Manual entry for s5p_hash_final(9) β€” this is the close-up-hash-and-calculate-digest moment, and it's lowkey iconic. πŸ¦‹

🌸 NAME 🌸

s5p_hash_final β€” close up hash and calculate digest. ✨

⭐ SYNOPSIS ⭐

int s5p_hash_final (struct ahash_request *req );

πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” AHASH request. That's the one and only argument, bestie. πŸ’…

πŸ”₯ NOTE πŸ”₯

okay so in final, req->src do not have any data, and req->nbytes can be non-zero. 🫢

If there were no input data processed yet and the buffered hash data is less than BUFLEN (64), then calculate the final hash immediately by using SW algorithm fallback. ✨

Otherwise enqueues the current AHASH request with OP_FINAL operation op and finalize hash message in HW. Note that if digcnt!=0 then there were previous update op, so there are always some buffered bytes in ctx->buffer, which means that ctx->bufcnt!=0. πŸ’€

πŸ‘‘ RETURN πŸ‘‘

  • 0 β€” if the request has been processed immediately. πŸŽ‰
  • -EINPROGRESS β€” if the operation has been queued for later execution or is set to processing by HW. ⏳
  • -EBUSY β€” if queue is full and request should be resubmitted later. 😭
  • other negative values β€” denotes an error. πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./drivers/crypto/s5p-sss.c plus the whole crew:


shoutout to the footer: source/version ./drivers/crypto, date October 2026 β€” iconic, periodt. πŸ’…

πŸ“¦ where this page comes from