sha224_update(9)
π sha224_update(9) β the Kernel API Manual moment
okay so bestie, welcome to sha224_update, a page straight out of the Kernel API Manual β¨. It's a tiny little function, but it's literally doing the Lord's work inside the SHA-224 machinery, and we're gonna talk about it.
π NAME
sha224_update β the girlies whose whole job is updating a SHA-224 context with message data. Fresh data in, context goes brrr. π
π¦ SYNOPSIS
void sha224_update (struct sha224_ctx *ctx , const u8 *data , size_t len
);
That return type being void? Iconic. It gives nothing and it slays anyway. π
πΈ ARGUMENTS
ctxβ the context to update. And listen π it must have been initialized first, okay? no cap, don't be out here passing a vibe-fresh uninitialized context, that's not the move πdataβ the message data. the actual content. the main character. βlenβ the data length in bytes. how many bytes ofdatawe're working with, fr fr π
π DESCRIPTION
You can call this any number of times. That's it. That's the whole description. Feed it data in chunks, call it again, call it a third time, keep going β the context just keeps absorbing your bytes like a bestie who never gets tired of your lore. π₯
lowkey the most chill function in the whole crypto header ngl β no drama, no weird edge cases in the docs, just any number of times π
π CONTEXT
Any context. Like, genuinely any. She's not picky, she's not exclusive, she fits wherever you need her π«Άβ¨
π SEE ALSO
okay bestie, buckle up, because this SEE ALSO list is long and honestly it ate π β every single one of these is here, no skipping:
- Kernel file
./include/crypto/sha2.h struct sha224_ctx(9)sha224_init(9)sha224_final(9)sha224(9)struct hmac_sha224_key(9)struct hmac_sha224_ctx(9)hmac_sha224_preparekey(9)hmac_sha224_init(9)hmac_sha224_init_usingrawkey(9)hmac_sha224_update(9)hmac_sha224_final(9)hmac_sha224(9)hmac_sha224_usingrawkey(9)struct sha256_ctx(9)sha256_init(9)sha256_update(9)sha256_final(9)sha256(9)sha256_finup_2x(9)sha256_finup_2x_is_optimized(9)struct hmac_sha256_key(9)struct hmac_sha256_ctx(9)hmac_sha256_preparekey(9)hmac_sha256_init(9)hmac_sha256_init_usingrawkey(9)hmac_sha256_update(9)hmac_sha256_final(9)hmac_sha256(9)hmac_sha256_usingrawkey(9)struct sha384_ctx(9)sha384_init(9)sha384_update(9)sha384_final(9)sha384(9)struct hmac_sha384_key(9)struct hmac_sha384_ctx(9)hmac_sha384_preparekey(9)hmac_sha384_init(9)hmac_sha384_init_usingrawkey(9)hmac_sha384_update(9)hmac_sha384_final(9)hmac_sha384(9)hmac_sha384_usingrawkey(9)struct sha512_ctx(9)sha512_init(9)sha512_update(9)sha512_final(9)sha512(9)struct hmac_sha512_key(9)struct hmac_sha512_ctx(9)hmac_sha512_preparekey(9)hmac_sha512_init(9)hmac_sha512_init_usingrawkey(9)hmac_sha512_update(9)hmac_sha512_final(9)hmac_sha512(9)hmac_sha512_usingrawkey(9)
like... the whole SHA-2 family reunion plus every HMAC cousin showed up. obsessed. πβ¨
and that's the page!! this lil beauty lives over in ./include/crypto and the version tag says October 2026 β so when you're flipping through sha224_update(9) and it all makes sense, just remember who told you π§π bye bestie, go hash something π
π¦ 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