linux-ext4 - Re: fallocate support for bitmap-based files

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 30 Jun 2007 10:31:45 -0400
From:	Mingming Cao <cmm@...ibm.com>
To:	Andreas Dilger <adilger@...sterfs.com>
Cc:	Mike Waychison <mikew@...gle.com>, Theodore Tso <tytso@....edu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Sreenivasa Busam <sreenivasac@...gle.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: fallocate support for bitmap-based files

On Sat, 2007-06-30 at 01:14 -0400, Andreas Dilger wrote:
> On Jun 29, 2007  18:26 -0400, Mike Waychison wrote:
> > Andreas Dilger wrote:
> > >I don't think ext2 is safe for > 8TB filesystems anyways, so this
> > >isn't a huge loss.
> > 
> > This is reference to the idea of overloading the high-bit and not 
> > related to the >PAGE_SIZE blocks correct?
> 
> Correct - just that the high-bit use wouldn't unduely impact the
> already-existing 8TB limit of ext2.
> 

The 8TB limit on mainline ext2 was simplely caused by kernel block
variable type bugs. The bug fixes were ported back from ext3 to ext2,
when reservation+simple-multiple-balloc were backported from ext3 to
ext2. I believe ext2 in mm tree is able to address 16TB in the kernel
side.  Not sure if there are remaining work to be done in e2fsck to
handle 16TB ext2, but I assume it's not huge work.

Mingming

-
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