1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-08 21:18:16 +03:00

ldb_kv_index: dn_list load sub transaction can re-use keys

We don't want to modify the original list, but we can reuse the keys
if we treat them as immutable and don't free them. That makes it a lot
quicker if there are many keys (i.e. where an index is useful) and may
sub-transactions. In particular, it avoids O(n²) talloc_memdups.

A removed comment that says "We have to free the top level index
memory otherwise we would leak", and this will be addressed in the
next commit.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15590

Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Stefan Metzmacher <metze@samba.org>
This commit is contained in:
Douglas Bagnall 2024-06-26 11:05:49 +12:00 committed by Douglas Bagnall
parent ed7bc50b00
commit 5f0198d698

View File

@ -447,34 +447,39 @@ static int ldb_kv_dn_list_load(struct ldb_module *module,
* There is an active index sub transaction, and the record was
* found in the primary index transaction cache. A copy of the
* record needs be taken to prevent the original entry being
* altered, until the index sub transaction is committed.
* altered, until the index sub transaction is committed, but we
* don't copy the actual values, just the array of struct ldb_val
* that points to the values (which are offsets into a GUID array).
*
* As a reminder, our primary cache is an in-memory tdb that
* maps attributes to struct dn_list objects, which point to
* the actual index, which is an array of struct ldb_val, the
* contents of which are {.data = <binary GUID>, .length =
* 16}. The array is sorted by GUID data, and these GUIDs are
* used to look up index entries in the main database. There
* are more layers of indirection than necessary, but what
* makes the index useful is we can use a binary search to
* find if the array contains a GUID.
*
* What we do in a sub-transaction is make a copy of the struct
* dn_list and the array of struct ldb_val, but *not* of the
* .data that they point to. This copy is put into a new
* in-memory tdb which masks the primary cache for the duration
* of the sub-transaction.
*
* In an add operation in a sub-transaction, the new ldb_val
* is a child of the sub-transaction dn_list, which will
* become the main dn_list if the transaction succeeds.
*
* These acrobatics do not affect read-only operations.
*/
{
struct ldb_val *dns = NULL;
size_t x = 0;
dns = talloc_array(
list,
struct ldb_val,
list2->count);
if (dns == NULL) {
return LDB_ERR_OPERATIONS_ERROR;
}
for (x = 0; x < list2->count; x++) {
dns[x].length = list2->dn[x].length;
dns[x].data = talloc_memdup(
dns,
list2->dn[x].data,
list2->dn[x].length);
if (dns[x].data == NULL) {
TALLOC_FREE(dns);
return LDB_ERR_OPERATIONS_ERROR;
}
}
list->dn = dns;
list->count = list2->count;
list->dn = talloc_memdup(list,
list2->dn,
talloc_get_size(list2->dn));
if (list->dn == NULL) {
return LDB_ERR_OPERATIONS_ERROR;
}
list->count = list2->count;
return LDB_SUCCESS;
/*
@ -3848,9 +3853,7 @@ int ldb_kv_reindex(struct ldb_module *module)
* Copy the contents of the nested transaction index cache record to the
* transaction index cache.
*
* During this 'commit' of the subtransaction to the main transaction
* (cache), care must be taken to free any existing index at the top
* level because otherwise we would leak memory.
* This is a 'commit' of the subtransaction to the main transaction cache.
*/
static int ldb_kv_sub_transaction_traverse(
struct tdb_context *tdb,
@ -3879,8 +3882,7 @@ static int ldb_kv_sub_transaction_traverse(
/*
* Do we already have an entry in the primary transaction cache
* If so free it's dn_list and replace it with the dn_list from
* the secondary cache
* If so replace dn_list with the one from the subtransaction.
*
* The TDB and so the fetched rec contains NO DATA, just a
* pointer to data held in memory.
@ -3893,21 +3895,37 @@ static int ldb_kv_sub_transaction_traverse(
abort();
}
/*
* We had this key at the top level. However we made a copy
* at the sub-transaction level so that we could possibly
* roll back. We have to free the top level index memory
* otherwise we would leak
* We had this key at the top level, and made a copy
* of the dn list for this sub-transaction level that
* borrowed the top level GUID data. We can't free the
* original dn list just yet.
*
* In this diagram, ... is the C pointer structure
* and --- is the talloc structure (::: is both).
*
* index_in_top_level ::: dn orig ..............
* | | :
* | `--GUID array :
* | |----- val1 data
* ldb_kv `----- val2 data
* | :
* index_in_subtransaction :: dn copy ..........:
* | :
* `------------ new val3 data
*
* So we don't free the index_in_top_level dn list yet,
* because we are (probably) borrowing most of its
* children.
*/
if (index_in_top_level->count > 0) {
TALLOC_FREE(index_in_top_level->dn);
}
index_in_top_level->dn
= talloc_steal(index_in_top_level,
index_in_subtransaction->dn);
index_in_top_level->count = index_in_subtransaction->count;
return 0;
}
/*
* We found no top level index in the cache, so we put one in.
*/
index_in_top_level = talloc(ldb_kv->idxptr, struct dn_list);
if (index_in_top_level == NULL) {
ldb_kv->idxptr->error = LDB_ERR_OPERATIONS_ERROR;