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.0611031428010.17427@artax.karlin.mff.cuni.cz>
Date:	Fri, 3 Nov 2006 14:31:46 +0100 (CET)
From:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To:	Jörn Engel <joern@...nheim.fh-wedel.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

>>> I am fully aware the counters are effectively 48-bit.  If they were
>>> just 32-bit, you would likely have hit the problem yourself already.
>>
>> Given the seek time 0.01s, 31-bit value would last for minimum time of 248
>> days when doing only syncs and nothing else. 47-bit value will last for
>> reasonably long.
>
> So you can at most do one transaction per drive seek?  That would
> definitely solve the overflow case, but hardly sounds like a
> high-performance filesystem. :)

Really it can batch any number of modifications into one transaction 
(unless fsync or sync is called). Transaction is closed only on 
fsync/sync, if 2 minutes pass (can be adjusted) or when the disk runs out 
of space.

Mikulas

Mikulas

> Jörn
>
> -- 
> Data expands to fill the space available for storage.
> -- Parkinson's Law
>