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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 11 May 2020 18:26:24 +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

--- Comment #7 from Eric Biggers (ebiggers3@...il.com) ---
> Someone might use a kernel with casefold or encryption support on Monday -
> and even use these features, causing a few of these flags to be set.
>
> The same person might run a kernel with casefold and/or encryption disabled
> on Tuesday. So, would it really be necessary to set their filesystem to ro -
> giving them a hard time, just because they like to use different kernels? I
> think not.

Casefold is an 'incompat' feature, because it changes the directory format.  So
if someone enables it (on-disk, which is different from merely using a kernel
that supports it), then old kernels can't use the filesystem at all.  That's
working as intended.

But that's *not* actually what this issue is about.  This issue is about how
the kernel treats inodes that got corrupted to have the casefold flag set when
the user didn't actually enable the casefold feature.  The ext4 feature flags
have clear behavior for how unexpected flags are handled, but the inode flags
don't.

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