https://bugzilla.kernel.org/show_bug.cgi?id=207635 --- Comment #7 from Eric Biggers (ebiggers3@xxxxxxxxx) --- > 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.
