| 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
| ||
|
Message-ID: <461A5F13.7040705@cfl.rr.com> Date: Mon, 09 Apr 2007 11:43:15 -0400 From: Phillip Susi <psusi@....rr.com> To: Samuel Thibault <samuel.thibault@...-lyon.org>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Add a norecovery option to ext3/4? Samuel Thibault wrote: > Hi, > > Distribution installers usually try to probe OSes for building a suited > grub menu. Unfortunately, mounting an ext3 partition, even in read-only > mode, does perform some operations on the filesystem (log recovery). > This is not a good idea since it may silently garbage data. XFS has a > norecovery option that allows to disable that, I'd say ext3/4 should > have it too. When the filesystem is told to mount the disk read only, that means it should not write to it. The fact that ext3 goes ahead and does anyway is a bug and should be fixed. There is no need for a norecovery option, because read only is a sufficient directive to tell the filesystem not to write to the disk. As someone else pointed out, this behavior causes havoc if you hibernate a system and then boot up another system which mounts the disk of the hibernated system. Under all conditions it should be safe to mount a disk read only, but here it is not because the journal playback trashes the disk out from under the hibernated system. - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists