https://bugzilla.kernel.org/show_bug.cgi?id=109331 Theodore Tso <tytso@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 CC| |tytso@xxxxxxx --- Comment #5 from Theodore Tso <tytso@xxxxxxx> --- The kernel's low-level boot path tries each file system --- and the problem is that ext4 doesn't know whether this is part of the boot process mounting the root file system, or the user explicitly trying to mount a file system as ext3. When we dropped support for ext3 in recent kernels, CONFIG_EXT4_USE_FOR_EXT23 was renamed CONFIG_EXT4_USE_FOR_EXT2 and the ext3 bug-for-bug backwards compatibility support was unconditionally included. It was just a side effect of how ext3 code was removed from the Linux kernel, and given that most distributions would never explicitly want to remove ext3 support entirely lest it break users' configs (i.e., so very, VERY few people compile kernels with !CONFIG_EXT2_FS, !CONFIG_EXT3_FS, and !CONFIG_EXT4_USE_FOR_EXT23) no one really noticed or cared. We can "fix" this by either changing CONFIG_EXT4_USE_FOR_EXT2 back to CONFIG_EXT4_USE_FOR_EXT23, which would support !ext2, !ext3compat, ext4, but not allow ext2, !ext3co,pat, or ext4. Or by adding a new Kconfig for EXT4_USE_FOR_EXT3 that would explicitly turn on/off just the ext3 compatibility code. Personally, I don't really care enough to implement this, but if someone wants to try their hand at a relatively simple kernel patch, please give it a try. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
