samba.git/lib/dbwrap/dbwrap.h, branch talloc-2.3.2

dbwrap: Make dbwrap_lock_order_[un]lock() public

2020-05-15T00:48:32+00:00

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

dbwrap: Pass "value" to dbwrap_do_locked() callback

2019-11-22T23:57:46+00:00

I want to reduce dbwrap_record_get_value(). It makes the caller believe it can
make a copy of the TDB_DATA returned and that the value remains constant. It's
not, as you can always do a dbwrap_record_store().

This patch removes one requirement for getting the value out of a
db_record via dbwrap_record_get_value(). You can still make a copy, but from an
API perspective to me it's more obvious that "value" as a parameter to the
callback has a limited lifetime.

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

lib: Allow a 4th lock order

2019-09-17T22:49:39+00:00

We will have another tdb soon

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

lib: Remove an obsolete comment

2019-09-10T23:14:31+00:00

At least as of 2ac9d0afa66 ctdb does not care about db prios anymore

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

dbwrap: Remove calls to loadparm

2018-04-23T23:53:19+00:00

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

dbwrap: Add dbwrap_do_locked

2017-07-25T15:43:16+00:00

With a proper implementation this enables modifications without
having to allocate a record. In really performance sensitive code
paths this matters.

Signed-off-by: Volker Lendecke 
Reviewed-by: Ralph Boehme

dbwrap: Add dbwrap_record_storev

2017-07-25T15:43:16+00:00

Signed-off-by: Volker Lendecke 
Reviewed-by: Ralph Boehme

dbwrap: Add dbwrap_merge_dbufs

2017-07-25T15:43:16+00:00

Transitional code to implement dbwrap_record_storev

Signed-off-by: Volker Lendecke 
Reviewed-by: Ralph Boehme

dbwrap: add dbwrap_parse_record_send/recv

2017-04-18T20:54:16+00:00

The req_state parameter tells the caller whether the async request is
blocked in a full send queue:

req_state >= DBWRAP_REQ_DISPATCHED := request is dispatched
req_state < DBWRAP_REQ_DISPATCHED := send queue is full

This is useful in a clustered Samba environment where the async dbwrap
request is sent over a socket to the local ctdbd.

If the send queue is full and the caller was issuing multiple async
dbwrap requests in a loop, the caller knows it's probably time to stop
sending requests for now and try again later.

This will be used in subsequent commits in
smbd_smb2_query_directory_send() when implementing async write time
updates. Directories may contain umpteen files so we send many requests
to ctdb without going through tevent and reading the responses which has
the potential to deadlock.

Signed-off-by: Ralph Boehme 
Reviewed-by: Stefan Metzmacher

dbwrap: add enum dbwrap_req_state

2017-04-18T20:54:16+00:00

This will be used by async dwrap_parse_send() as an out argument, giving
the caller an indication about the state of the request.

This is can be useful for the caller if it is a sync function and sends
multiple async dbwrap requests. As it's a sync function it won't return
to the main tevent event loop and so the async dbwrap recv function are
not called.

As a result the function may deadlock: our receive queue may already be
full with results from a peer, the peer might be blocked in his send
queue (because we're not receiving), the peer therefor doesn't read from
his receive queue so our send queue will block as well.

To inform the caller of this situation "send queue full" we return this
state information to the caller of the dbwrap send function.

Signed-off-by: Ralph Boehme 
Reviewed-by: Stefan Metzmacher