samba.git/lib/ntdb/test, branch master

ntdb: Fix control reaches end of non-void function.

2014-11-28T13:24:07+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Guenther Deschner

lib/ntdb optimize includes in ntdb tests

2013-12-07T15:45:15+00:00

use the private header (which will use libreplace or system headers)
instead of direct includes of system includes

Signed-off-by: Christian Ambach 
Reviewed-by: Rusty Russell

pyntdb: Add tests for Python API.

2013-12-06T04:21:03+00:00

Signed-off-by: Jelmer Vernooij 

Reviewed-by: Andrew Bartlett

ntdb: don't call open hook when re-opening an existing database.

2013-03-23T08:39:50+00:00

In particular, the Samba dbwrap wrapper can do this for schannel_store,
with the openhook set to clear the database if it can get the lock
(which, being in the same process, it can).

Signed-off-by: Rusty Russell 

Autobuild-User(master): Rusty Russell 
Autobuild-Date(master): Sat Mar 23 09:39:50 CET 2013 on sn-devel-104

ntdb: fix database corruption when transaction doesn't change anything.

2013-02-20T04:31:19+00:00

ntdb's transaction code has an optimization which tdb's doesnt: it
only writes the parts of blocks whose contents have changed.  This
means we can actually have a transaction which turns out to need no
recovery region.

This breaks the recovery setup logic, which sets the current recovery
size to 0 if there's no recovery area, and assumes that we'll always
create a new recovery area since the recovery will always need > 0
bytes.

In fact, if we really haven't changed anything, we can skip the
transaction commit altogether: since this happens at least once with
Samba, it's worth doing.

Signed-off-by: Rusty Russell 
Reviewed-by: Andrew Bartlett

lib/ntdb: Fix format string errors found by -Werror=format in ntdb tests

2012-07-30T04:25:10+00:00

ntdb: test arbitrary operations during ntdb_parse_record().

2012-06-22T05:35:17+00:00

In particular, this tests that we can store enough records to make the
database expand while we map the given record.  We use a global lock for
this, but it could happen in theory with another process.

It also tests the that we can recurse inside ntdb_parse_record().

Signed-off-by: Rusty Russell

ntdb: make database read-only during ntdb_parse() callback.

2012-06-22T05:35:17+00:00

Since we have a readlock, any write will grab a write lock: if it happens
to be on the same bucket, we'll fail.

For that reason, enforce read-only so every write operation fails
(even for NTDB_NOLOCK or NTDB_INTERNAL dbs), and document it!

Signed-off-by: Rusty Russell

ntdb: don't munmap the database on every close.

2012-06-22T05:35:17+00:00

Since we can have multiple openers, we should leave the mmap in place
for the other openers to use.  Enhance the test to check the bug (it
still works, because without mmap we fall back to read/write, but
performance would be terrible!).

Signed-off-by: Rusty Russell

ntdb: respect TDB_NO_FSYNC flag for 'make test'

2012-06-22T05:35:16+00:00

This reduces test time from 31 seconds to 6, on my laptop.

Signed-off-by: Rusty Russell