polyval_update(9)

💅 polyval_update(9) — or, "how to feed your hash bestie more data"

okay so this page lives in the Kernel API Manual, and it's all about polyval_update(9) — literally the glow-up function that keeps your POLYVAL context fed. 🦋

---

✨ NAME ✨

polyval_update — Update a POLYVAL context with message data

---

🎀 SYNOPSIS 🎀

void polyval_update (struct polyval_ctx *ctx , const u8 *data , size_t
len );

like… that's the whole vibe. no return value, it just does the thing. 💅

---

🌸 ARGUMENTS 🌸

• ctx — the context you're updating; it must have been initialized first, no cap. an uninitialized ctx is not the main character energy we're going for 🙈
• data — the message data itself, the actual content, the moment. ✨
• len — how long data is, in bytes. and lowkey the best part: it doesn't need to be block-aligned. feed it whatever size you want, she's not picky 🫶

---

💖 DESCRIPTION 💖

This can be called any number of times.

(yes bestie, any number. zero, one, fifty, a million. go off. 🔥)

---

🧚 CONTEXT 🧚

Any context. literally any. it's giving flexible. 🌈

---

👑 SEE ALSO 👑

Kernel file ./include/crypto/gf128hash.h, plus the whole friend group:

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), polyval_export_blkaligned(9), ghash_update(9), ghash_final(9), polyval_final(9), ghash(9), polyval(9)

---

ngl, if you're calling polyval_update before polyval_init, that's on you — the ctx has to be initialized first or the vibes are off. 😭

---

and that's the page!! mwah 💋 it lives in ./include/crypto, dated October 2026 — see you in the next man page, bestie 🎀🦋💜