linux-ext4 - Re: persistent preallocation

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: <20100803180631.GA9453@thunk.org>
Date:	Tue, 3 Aug 2010 14:06:31 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Bo Brantén <bosse@....umu.se>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: persistent preallocation

On Tue, Aug 03, 2010 at 12:58:21PM +0200, Bo Brantén wrote:
> 
> I have a question on the implementation of persistent preallocation,
> the reason to not return the disk block is because it can contain
> old data but I wonder if an implementation has to return zeros
> instead or if it could return any garbage as long as it is not
> _that_ garbage?

What would be the point?  If we know that we can't return the on-disk
block contents, returning all zero's is much nicer for the application
since it also then looks like and works just like a sparse file.

      	      	   	      	  	- 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