linux-ext4 - Re: What's cooking in e2fsprogs.git (topics)

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: <8263yw2zey.fsf@mid.bfk.de>
Date:	Tue, 18 Dec 2007 09:13:41 +0100
From:	Florian Weimer <fweimer@....de>
To:	Theodore Tso <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org, Eric Sandeen <esandeen@...hat.com>
Subject: Re: What's cooking in e2fsprogs.git (topics)

* Theodore Tso:

> Hm.  I was very concerned about using db4, mainly because of the ABI
> and on-disk format compatibility nightmare, which is why I chose tdb.

If you don't use the transactional data store, the B-tree disk format
hasn't changed in years.  The API is fairly stable, too (not the ABI,
of course, because it's deliberately tied to a particular version by
most distros).

The main issues I see with Berkeley DB are: it assumes atomic page
writes (even in transactional data store mode), it writes database
files in a way that maximizes file-system level fragmentation, and
sequential scans are unbearably slow.  Oh, and most applications using
TDS do not handle recovery and upgrades properly. (For them, SQLite
would probably have been a better choice. 8-/)

-- 
Florian Weimer                <fweimer@....de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99
-
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