ceph_fscrypt...pare_readdir(9)

💅 ceph_fscrypt_prepare_readdir — the Kernel API manual, but make it make sense ✨

okay so bestie, you're in the Kernel API Manual and this function lives in the ceph_fscrypt...pare_readdir corner of the world 💖 (yes the title is doing that abbreviation thing, it's the ceph_fscrypt_prepare_readdir function, iykyk 🎀).

---

🌸 NAME 🌸

ceph_fscrypt_prepare_readdir — literally just a simple __fscrypt_prepare_readdir() wrapper, no cap 🫶

---

✨ SYNOPSIS ✨

int ceph_fscrypt_prepare_readdir (struct inode *dir );

---

🎀 ARGUMENTS 🎀

• dir — the directory inode you're prepping for readdir, that's it, that's the whole vibe 🦋

---

💅 DESCRIPTION 💅

So this is a simple wrapper around __fscrypt_prepare_readdir 💖 The one extra little thing it does? If this call results in the directory actually getting unlocked, it marks the directory as non-complete. That's the whole personality. Iconic, lowkey 🧚

---

🌈 RETURN 🌈

• 1 — the directory was locked and the key is now loaded, i.e. the dir is unlocked, slay 🔥
• 0 — the directory is still locked 🙈
• < 0 — __fscrypt_prepare_readdir failed, and that's the sad path 😭

fr fr, watch that < 0 — negative means a failure from __fscrypt_prepare_readdir, so don't just check for truthy, bestie 💀

---

🦋 SEE ALSO 🦋

• Kernel file ./fs/ceph/crypto.c
• ceph_fname_to_usr(9)
• ceph_fscrypt_decrypt_pages(9)
• ceph_fscrypt_decrypt_extents(9)
• ceph_fscrypt_encrypt_pages(9)

---

⭐ and that's the whole page, bestie 💜 this lil number comes from ./fs/ceph, dated October 2026, and it signs off being the ceph_fscrypt...pare_readdir(9) manual — go forth and readdir responsibly 👑🌸