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: <4D95B36D-5AB6-4CF6-8BCA-03E0562F3ED3@dilger.ca> Date: Mon, 31 Aug 2015 18:23:01 -0600 From: Andreas Dilger <adilger@...ger.ca> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org> Subject: Re: [GIT PULL] Ext3 removal, quota & udf fixes On Aug 31, 2015, at 3:37 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > On Sun, Aug 30, 2015 at 11:19 PM, Jan Kara <jack@...e.cz> wrote: >> >> The biggest change in the pull is the removal of ext3 filesystem driver >> (~28k lines removed). > > I really am not ready to just remove ext3 without a lot of good > arguments. There might well be people who this use ext3 as ext3, and > don't want to update. I want more a rationale for removal than "ext4 > can read old ext3 filesystems". The ext4 code can read and write ext3 filesystems without any compatibility issues (i.e. none of the ext4-specific features are enabled automatically) and have been doing so for all RHEL and SLES users for the past several years via the CONFIG_EXT4_USE_FOR_EXT23 option (added in commit 24b58424 in 2009). It looks like the same for Ubuntu since early 2014 also. The ext4-specific features either need to be enabled specifically via tune2fs (if possible) or at mkfs time. Cheers, Andreas -- 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