crypto_alloc_acomp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ crypto_alloc_acomp(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual β€” this is the page for crypto_alloc_acomp, and it's literally about getting you a compression handle. let's go πŸ’…


✨ NAME ✨

crypto_alloc_acomp β€” allocate ACOMPRESS tfm handle πŸ¦‹


✨ SYNOPSIS ✨

struct crypto_acomp * crypto_alloc_acomp (const char *alg_name , u32 type , u32 mask );

like, that's the whole call. one function, three args, no cap.


✨ ARGUMENTS ✨

  • alg_name β€” this is the cra_name / name or the cra_driver_name / driver name of the compression algorithm, e.g. "deflate". basically you're telling the kernel which algorithm you want πŸ“
  • type β€” specifies the type of the algorithm. yes queen, the type.
  • mask β€” specifies the mask for the algorithm. and the mask. they're a lil duo πŸ’œ

✨ DESCRIPTION ✨

So what does it actually do? It allocates a handle for a compression algorithm πŸ”₯

The returned struct crypto_acomp is the handle β€” and it's required for any subsequent API invocation for the compression operations. so like, no handle = no compression, that's just the vibe check ✨


✨ RETURN ✨

  • On success? you get the allocated handle πŸ˜ŒπŸ‘‘
  • On error? IS_ERR is true, and PTR_ERR returns the error code. so check your errors, bestie, don't be out here dereferencing a bad pointer πŸ˜­πŸ’€

🌈 SEE ALSO 🌈

okay this list is long, but every single one of these is iconic in its own right:

go read them. all of them. main character reading list fr fr πŸ“šβœ¨


and that's the page! this lil beauty lives in ./include/crypto, and it's dated October 2026 β€” so yeah, she's from the future πŸ’« slay, and remember: allocate responsibly πŸ«ΆπŸ’–

πŸ“¦ where this page comes from