https://bugzilla.kernel.org/show_bug.cgi?id=207635 Christian Kujau (lists@xxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lists@xxxxxxxxxxxxxxx --- Comment #6 from Christian Kujau (lists@xxxxxxxxxxxxxxx) --- (In reply to Joerg M. Sigle from comment #5) > 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 - I don't know about the inner workings of this particular issue here, but turning the filesystem to RO when errors are encountered - isn't this what the "error-behavior" flag controls? $ tune2fs -l /dev/sda1 | grep ^Err Errors behavior: Remount read-only Setting this to "continue" or "panic" should have avoided that whole "RO" situation, I guess. -- You are receiving this mail because: You are watching the assignee of the bug.
