Even though it seems to be able to resolve some names of
case-insensitive directories, the lack of d_hash and d_compare means we
end up with a broken state in the d_cache.  Considering it was never a
goal to support these two together, and we are preparing to use
d_revalidate in case-insensitive filesystems, which would make the
combination even more broken, reject any attempt to get a casefolded
inode from ecryptfs.

Signed-off-by: Gabriel Krisman Bertazi <kris...@suse.de>

---
Changes since v5:
  - Check IS_CASEFOLDED directly (Eric)
---
 fs/ecryptfs/inode.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c
index 83274915ba6d..01ec2250e40f 100644
--- a/fs/ecryptfs/inode.c
+++ b/fs/ecryptfs/inode.c
@@ -78,6 +78,14 @@ static struct inode *__ecryptfs_get_inode(struct inode 
*lower_inode,
 
        if (lower_inode->i_sb != ecryptfs_superblock_to_lower(sb))
                return ERR_PTR(-EXDEV);
+
+       /* Reject dealing with casefold directories. */
+       if (IS_CASEFOLDED(lower_inode)) {
+               pr_err_ratelimited("%s: Can't handle casefolded directory.\n",
+                                  __func__);
+               return ERR_PTR(-EREMOTE);
+       }
+
        if (!igrab(lower_inode))
                return ERR_PTR(-ESTALE);
        inode = iget5_locked(sb, (unsigned long)lower_inode,
-- 
2.41.0



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to