linux-ext4 - Re: Make huge files strictly contiguous (fallocate, bigalloc, e4defrag...)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140420200030.GC29727@thunk.org>
Date:	Sun, 20 Apr 2014 16:00:30 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Contact <neitsab@....fr>
Cc:	Lukáš Czerner <lczerner@...hat.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Make huge files strictly contiguous (fallocate, bigalloc,
 e4defrag...)

On Sun, Apr 20, 2014 at 09:38:30PM +0200, Contact wrote:
> > Note that because this uses a new compat feature, "sparse_super2", if
> > you use the new mke2fs to create such a file system, you will also
> > need to make sure the file system is checked using a version of e2fsck
> > that supports this new feature as well.  No kernel changes are
> > required to support this, though.
> >
> Any plans to get this feature into master at some point in the 
> development?

The maint branch is regularly merged into the master and next
branches, so it's there today.  The maint branch will very shortly be
the source of a 1.42.10 maintenance release.

The master branch will eventualy be a 1.43 release; it has some much
more disruptive changes, and adds support for metadata checksums,
inline data, etc.  It's likely that 1.42.10 will be the last
maintenance release, and the focus will be on stablizing 1.43 and
making sure we're really ready to support the ABI's for the new
library functions in libext2fs to support these new features _forever_.

Cheers,

					- 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