| 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
| ||
|
Date: Wed, 23 Jan 2008 14:50:29 -0700 From: Andreas Dilger <adilger@....com> To: Theodore Tso <tytso@....EDU> Cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org Subject: Re: [PATCH, RFC] Add new "development flag" to the ext4 filesystem On Jan 23, 2008 11:53 -0500, Theodore Tso wrote: > Since I'm still hoping that > some point in the future, fs/ext4 could subsume fs/ext3 so we don't > have to worry about bug fixes going into fs/ext2 AND fs/ext3 AND > fs/ext4, I have my own reasons for wanting that. If any newbie kernel hacker wants a filesystem project, allowing ext4 to mount ext2 filesystems w/o a journal would be very useful. I suspect that a simple flag check in the ext4_journal_* wrappers of the jbd2 functions would be enough in many cases. One of the reasons to keep ext2 around is that ext3 cannot mount the filesystem without a journal, and removing that limitation for ext4 would bring us one step closer to removing a ton of duplicate code. Another reason for ext2 vs. ext3 was overhead from journaling, and that could also be removed by allowing ext4 to mount ext2 filesystems w/o a journal. Maybe a good proposal for a Google Summer-of-Code project. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. - 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