samba.git/lib/tdb/common/lock.c, branch talloc-2.4.3

lib:tdb: Fix code spelling

2023-04-14T05:25:33+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Joseph Sutton

tdb: fix studio compiler build

2020-11-10T06:53:43+00:00

Solaris Studio compiler 12.4 is pedantic about prototypes in headers having
the external visibility declarations too. It throws errors like:

redeclaration must have the same or more restrictive linker scoping: ...

Signed-off-by: Bjoern Jacke 
Reviewed-by: Andrew Bartlett

lib/tdb: clang: Fix warning: Dereference of null pointer

2019-06-26T10:30:23+00:00

Fixes:

lib/tdb/common/lock.c:933:6: warning: Dereference of null pointer <--[clang]
        if (tdb->allrecord_lock.count) {
            ^~~~~~~~~~~~~~~~~~~~~~~~~

Signed-off-by: Noel Power 
Reviewed-by: Gary Lockyer

tdb: Fix a typo

2018-10-29T22:36:24+00:00

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

tdb: document hashtable bucket offset calculation madness

2017-08-22T21:32:13+00:00

Signed-off-by: Ralph Boehme 
Reviewed-by: Jeremy Allison

tdb: Improve debugging when the allrecord lock fails to upgrade

2017-04-27T12:52:17+00:00

Pair-Programmed-With: Stefan Metzmacher 

Signed-off-by: Andrew Bartlett 
Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andreas Schneider

tdb: Do lock upgrades properly

2017-04-10T18:44:21+00:00

When a process holds a readlock and wants to upgrade, this needs to be
reflected in the underlying lock. Without this, it is possible to cheat:
One process holds a readlock, and another process wants to write this
record. All the writer has to do is take a readonly lock on the key and
then do the store.

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

tdb: Fix some signed/unsigned hickups

2017-04-10T18:44:21+00:00

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

tdb: introduce tdb_chainlock_read_nonblock(), a nonblock variant of tdb_chainlock_read()

2015-04-28T19:28:18+00:00

Signed-off-by: Alexander Drozdov 
Reviewed-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

tdb: add TDB_MUTEX_LOCKING support

2014-05-22T19:05:15+00:00

This adds optional support for locking based on
shared robust mutexes.

The caller can use the TDB_MUTEX_LOCKING flag
together with TDB_CLEAR_IF_FIRST after verifying
with tdb_runtime_check_for_robust_mutexes() that
it's supported by the current system.

The caller should be aware that using TDB_MUTEX_LOCKING
implies some limitations, e.g. it's not possible to
have multiple read chainlocks on a given hash chain
from multiple processes.

Note: that this doesn't make tdb thread safe!

Pair-Programmed-With: Stefan Metzmacher 
Pair-Programmed-With: Michael Adam 
Signed-off-by: Volker Lendecke 
Signed-off-by: Stefan Metzmacher 
Signed-off-by: Michael Adam 
Reviewed-by: Jeremy Allison