linux-kernel - Re: New filesystem for Linux

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]

Message-ID: <Pine.LNX.4.64.0611040313280.28640@twinlark.arctic.org>
Date:	Sat, 4 Nov 2006 03:13:46 -0800 (PST)
From:	dean gaudet <dean@...tic.org>
To:	Jörn Engel <joern@...nheim.fh-wedel.de>
cc:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

On Sat, 4 Nov 2006, Jörn Engel wrote:

> On Fri, 3 November 2006 11:00:58 -0800, dean gaudet wrote:
> > 
> > it seems to me that you only need to be able to represent a range of the 
> > most recent 65536 crashes... and could have an online process which goes 
> > about "refreshing" old objects to move them forward to the most recent 
> > crash state.  as long as you know the minimm on-disk crash count you can 
> > use it as an offset.
> 
> You really don't want to go down that path.  Doubling the storage size
> will double the work necessary to move old objects - hard to imagine a
> design that scales worse.

there's no doubling of storage size required.

-dean