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: <47A0F98C.1080304@yahoo.de> Date: Wed, 30 Jan 2008 23:26:20 +0100 From: supersud501 <supersud501@...oo.de> To: Theodore Tso <tytso@....EDU> CC: linux-ext4@...r.kernel.org Subject: Re: [PATCH, RFC] Add new "development flag" to the ext4 filesystem Theodore Tso wrote: > 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 > > how can i set this "flag" on my filesystem? i've never set any flags before so i just removed the code from ext4-module to mount my filesystems, but setting the flag once would make it easier i think :) - 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