polyval_export_blkaligned(9)
π polyval_export_blkaligned(9) β Kernel API Manual π
okay so bestie, we're in the Kernel API Manual today and the star of the show is polyval_export_blkaligned(9). yes that's a mouthful, no you don't have to say it out loud. let's get into it πΈ
β¨ NAME β¨
polyval_export_blkaligned β literally just exports a POLYVAL accumulator value. that's the whole job. she's focused, she's straightforward, she ate π
π¦ SYNOPSIS π¦
void polyval_export_blkaligned (const struct polyval_ctx *ctx , struct
polyval_elem *acc );
π ARGUMENTS π
ctxβ the context you're pulling the accumulator value out of. this is the source, the origin story, the main character π«Άaccβ (output) the exported accumulator value lands here. it's giving "you get the result, congrats" β¨
β DESCRIPTION β
so what actually happens? this exports the accumulator from a POLYVAL context. simple, clean, iconic.
π¨ vibe check / important caveat: the number of data bytes processed so far must be a multiple of POLYVAL_BLOCK_SIZE. no cap, this is not optional. if it's not a multiple, that's not the moment, bestie π
π SEE ALSO π
- Kernel file
./include/crypto/gf128hash.h struct polyval_elem(9)struct ghash_key(9)struct polyval_key(9)struct ghash_ctx(9)struct polyval_ctx(9)ghash_preparekey(9)polyval_preparekey(9)ghash_init(9)polyval_init(9)polyval_import_blkaligned(9)ghash_update(9)polyval_update(9)ghash_final(9)polyval_final(9)ghash(9)polyval(9)
and that's the page!! π§ this lil gem lives under ./include/crypto and the version we're looking at is dated October 2026. ok bye bestie, go export those accumulators responsibly ππ₯
π¦ 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