tdb: test that new-style TDBs with non-default hashes can't be opened.
authorRusty Russell <rusty@rustcorp.com.au>
Fri, 10 Sep 2010 03:20:16 +0000 (12:50 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Fri, 10 Sep 2010 03:20:16 +0000 (12:50 +0930)
commitfdf3c148052f30d10e8c72fbdbdaf67d4a51b11e
tree27569d45b368bbfe6ab891dd492537ea81ea811c
parent63bceea014e091a2f2907e49f7c3b33f042106f4
tdb: test that new-style TDBs with non-default hashes can't be opened.

We currently allow opening of a TDB without any idea if we're using the
right hash function.  Since most people use the default, this hasn't been
a big issue.

The next change will put an example hash value in the rwlocks field in
the header: current TDB already refuses to open a TDB with this field
non-zero.  This commit simply adds tests that that occurs.
ccan/tdb/_info
ccan/tdb/test/jenkins-be-hash.tdb [new file with mode: 0644]
ccan/tdb/test/jenkins-le-hash.tdb [new file with mode: 0644]
ccan/tdb/test/run-wronghash-old.c [new file with mode: 0644]