fscrypt_supported_policy(9)

💅 fscrypt_supported_policy(9)

okay so this is a kernel API manual page, bestie — fscrypt_supported_policy(9), no cap. sit down, grab a lil snack 🍓, and let's get into it.

---

✨ NAME ✨

fscrypt_supported_policy — the vibe check that tells you whether an encryption policy is actually supported 👑

---

🎀 SYNOPSIS 🎀

bool fscrypt_supported_policy (const union fscrypt_policy *policy_u ,
const struct inode *inode );

like, it returns a bool, takes two things, that's the whole thing 🦋

---

🌸 ARGUMENTS 🌸

• policy_u — the encryption policy in question, the main character of this whole function 💖
• inode — the inode on which the policy will be used, i.e. where this policy is gonna live its life 🏠

---

💫 DESCRIPTION 💫

so here's the tea: you hand over an encryption policy, and this function checks whether all its encryption modes and other settings are actually supported by this kernel, on the given inode. literally all of them. every single mode, every setting. it's thorough like that ✨

⚠️ but — and this is the important part, don't skip it — it doesn't currently check for crypto API support here. (the original literally says "we don't currently don't check", double negative and all, we're keeping that energy 💀). so if you try to use an algorithm that isn't configured into the crypto API, it will still fail later. later later. not now. just so you know 🙈

---

🔥 RETURN 🔥

• true if supported 😌✨
• else false 😭

that's it. that's the return value. slay.

---

🫶 SEE ALSO 🫶

Kernel file ./fs/crypto/policy.c plus the whole friend group:

• fscrypt_policies_equal(9)
• fscrypt_new_context(9)
• fscrypt_policy_from_context(9)
• fscrypt_has_permitted_context(9)
• fscrypt_context_for_new_inode(9)
• fscrypt_set_context(9)
• fscrypt_parse_test_dummy_encryption(9)
• fscrypt_dummy_policies_equal(9)
• fscrypt_show_test_dummy_encryption(9)

---

okay that's the whole page, mwah 💋 — brought to you by the fine people at ./fs/crypto, dated October 2026. go forth and check your policies, bestie 🌈⭐