crypto_free_acomp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_free_acomp β€” free ACOMPRESS tfm handle

okay so this is crypto_free_acomp(9) from the Kernel API Manual, and honestly? she's short, she's sweet, she's the cleanup queen of the Asynchronous Compression API. bestie, this is the function you call when you're done with an ACOMPRESS tfm handle and you want to give that memory back before it becomes a leak you have to explain in code review 😭


✨ SYNOPSIS ✨

void crypto_free_acomp (struct crypto_acomp *tfm );

that's it. that's the whole vibe. no return value, she just frees and dips 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • tfm β€” the ACOMPRESS tfm handle, and it's gotta be one that was allocated with crypto_alloc_acomp. that's the matching pair, iykyk β€” you allocate it with crypto_alloc_acomp, you free it with crypto_free_acomp. iconique symmetry πŸ’–

🌸 DESCRIPTION 🌸

so here's the tea: this function frees the ACOMPRESS tfm handle you hand it.

and the actually important part β€” if tfm is a NULL pointer or an error pointer, this function does nothing. not a crash, not a warning, not a dramatic exit. she just quietly returns like nothing happened. no cap, it's genuinely that chill πŸ’…

fr fr this is the safe-cleanup behaviour: NULL or error pointer in, nothing happens out. so yes, you still pass it whatever you've got πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

go read the family, bestie, they all live together 🌈

(yes, acomp_request_alloc_extra(9) is listed twice in the original list β€” and we're keeping it twice, because accuracy is the moment, periodt ✨)


⭐ the cute lil sign-off ⭐

source file: ./include/crypto Β· dated October 2026 Β· this has been crypto_free_acomp(9), in the Kernel API Manual πŸ§šπŸ’œ

now go free that handle, bestie β€” memory leaks are not the aesthetic πŸŽ€πŸ”₯

πŸ“¦ where this page comes from