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: <20080122231707.GA21968@mit.edu> Date: Tue, 22 Jan 2008 18:17:08 -0500 From: Theodore Tso <tytso@....EDU> To: linux-ext4@...r.kernel.org Subject: [PATCH, RFC] Add new "development flag" to the ext4 filesystem As discussed on RFC, this flag is simply a generic "this is a crash/burn test filesystem" marker. If it is set, then filesystem code which is "in development" will be allowed to mount the filesystem. Filesystem code which is not considered ready for prime-time will check for this flag, and if it is not set, it will refuse to touch the filesystem. As we start rolling ext4 out to distro's like Fedora, et. al, this makes it less likely that a user might accidentally start using ext4 on a production filesystem; a bad thing, since that will essentially make it be unfsckable until e2fsprogs catches up. - Ted View attachment "kernel.patch" of type "text/x-diff" (1408 bytes) View attachment "e2fsprogs.patch" of type "text/x-diff" (4837 bytes)
Powered by blists - more mailing lists