linux-ext4 - [Bug 207635] EXT4-fs error (device sda3): ext4_lookup:1701: inode #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3): Remounting filesystem read-only

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 10 May 2020 22:06:23 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 207635] EXT4-fs error (device sda3): ext4_lookup:1701: inode
 #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3):
 Remounting filesystem read-only

https://bugzilla.kernel.org/show_bug.cgi?id=207635

Eric Biggers (ebiggers3@...il.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebiggers3@...il.com

--- Comment #3 from Eric Biggers (ebiggers3@...il.com) ---
It sounds like the problem is that one of the inodes on your filesystem was
previously corrupted in such a way that it had unknown flags set.

Then one of these flags was assigned a meaning, causing things to break.

Running e2fsck v1.45.4 or later on the filesystem should fix this by clearing
the casefold flag.  Can you try that?

I'm not sure there's anything else to do here, unless we were to make the
kernel ignore unexpected flags.  Ted, have you considered that?  And it is
intentional that e2fsck ignores unknown flags?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.