From: Gabriel Krisman Bertazi <kris...@collabora.com>

If the volume is in strict mode, ext4_ci_compare can report a broken
encoding name.  This will not trigger on a bad lookup, which is caught
earlier, only if the actual disk name is bad.

Signed-off-by: Gabriel Krisman Bertazi <kris...@collabora.com>
Signed-off-by: Eugen Hristev <eugen.hris...@collabora.com>
---
 fs/ext4/namei.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
index 2d0ee232fbe7..3268cf45d9db 100644
--- a/fs/ext4/namei.c
+++ b/fs/ext4/namei.c
@@ -1477,6 +1477,9 @@ static bool ext4_match(struct inode *parent,
                         * only case where it happens is on a disk
                         * corruption or ENOMEM.
                         */
+                       if (ret == -EINVAL)
+                               EXT4_ERROR_INODE(parent,
+                                       "Directory contains filename that is 
invalid UTF-8");
                        return false;
                }
                return ret;
-- 
2.34.1



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

Reply via email to