crypto_has_ahash(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_has_ahash β€” bestie, is this ahash even there?

okay so welcome to the Kernel API Manual entry for crypto_has_ahash, and yes we are absolutely getting into it πŸ’–


✨ NAME ✨

crypto_has_ahash β€” the little vibe check that tells you whether an ahash exists at all πŸ”

Like, it literally just searches for the availability of an ahash. That's the whole job. Iconic, honestly.


🌸 SYNOPSIS 🌸

int crypto_has_ahash (const char *alg_name , u32 type , u32 mask );

three arguments, one int out the door, no drama πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • alg_name β€” this is the cra_name / name, or the cra_driver_name / driver name, of the ahash you're asking about πŸ’« so you can slide in with the friendly name or the full government driver name, both work.
  • type β€” specifies the type of the ahash. yeah. that's the whole description. it's giving mysterious but okay πŸ‘‘
  • mask β€” specifies the mask for the ahash. and that's it, that's the tea 🍡

πŸ”₯ RETURN πŸ”₯

  • returns true when the ahash is known to the kernel crypto API βœ…
  • returns false otherwise ❌

no cap, that's the entire contract. either it's in the API or it's not, and now you know πŸ™Œ

heads up bestie: the signature says int but the return section talks about true / false β€” that's just how the page tells it, so don't come for me about it 😭

πŸ’œ SEE ALSO πŸ’œ

okay this list is LONG, like, scroll-for-a-while long, but every single one of them is here because I would never do you dirty like that 🫢

like half of these are the async ahash girlies and the other half are the sync shash girlies and honestly both ate πŸ’…


✨ that's the whole page, bestie ✨

this lil masterpiece lives under ./include/crypto in the source tree, dated October 2026, and it's filed as crypto_has_ahash(9) β€” go forth and check your hashes, ily, bye πŸŽ€πŸ’–πŸ§š

πŸ“¦ where this page comes from