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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0611030217570.7781@artax.karlin.mff.cuni.cz>
Date:	Fri, 3 Nov 2006 02:19:05 +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

> On Thu, 2 November 2006 22:52:47 +0100, Mikulas Patocka wrote:
>>
>> new method to keep data consistent in case of crashes (instead of
>> journaling),
>
> Your 32-bit transaction counter will overflow in the real world.  It
> will take a setup with millions of transactions per second and even
> then not trigger for a few years, but when it hits your filesystem,
> the administrator of such a beast won't be happy at all. :)
>
> Jörn

If it overflows, it increases crash count instead. So really you have 2^47 
transactions or 65536 crashes and 2^31 transactions between each crash.

Mikulas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ