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, 1 Oct 2014 08:34:11 -0400 From: Theodore Ts'o <tytso@....edu> To: Eric Sandeen <sandeen@...hat.com> Cc: ext4 development <linux-ext4@...r.kernel.org> Subject: Re: [PATCH] e2fsprogs: add large_file to base mkfs features On Tue, Sep 30, 2014 at 10:26:03PM -0500, Eric Sandeen wrote: > large_file (> 2G) support has been around since at least kernel 2.4; > mkfs of any sufficiently large filesystem sets it "accidentally" > when the resize inode exceeds 2G. This leaves very small > filesystems lacking the feature, which potentially changes > their behavior & codepaths the first time a > 2G file gets > written. > > There's really no reason to be making fresh filesystems which > strive to keep compatibility with 10 year old kernels; just > enable large_file at mkfs time. This is particularly obvious > for ext4 fielsystems, which set huge_file by default, but not > necessarily large_file. > > If old-kernel compatibility is desired, mke2fs.conf can be > modified locally to remove the feature. > > Signed-off-by: Eric Sandeen <sandeen@...hat.com> Applied, thanks. - Ted -- 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