summaryrefslogtreecommitdiffstats
path: root/source3/lib/dbwrap_rbt.c
Commit message (Collapse)AuthorAgeFilesLines
* s3-talloc Change TALLOC_ZERO_P() to talloc_zero()Andrew Bartlett2011-06-091-1/+1
| | | | | Using the standard macro makes it easier to move code into common, as TALLOC_ZERO_P isn't standard talloc.
* s3-build: use dbwrap.h only where needed.Günther Deschner2010-08-261-0/+1
| | | | Guenther
* Implement db_rbt_traverseVolker Lendecke2009-08-081-4/+33
|
* s3: Fix a memleak in dbwrap_rbt.Michael Adam2009-03-041-4/+4
| | | | | | | | | | | | | The SMB_MALLOC'ed rbt node data was not free'd on talloc free of the db context. This is a quick fix using talloc instead of malloc for allocation of the node data. Since malloc was originally used for performance reasons, one might want to reverse to malloc and create a talloc destructor that walks the tree and frees all the node data if this talloc approach proves to be too slow.. Michael
* Move rbtree.[ch] to lib/util.Jelmer Vernooij2008-10-121-1/+1
|
* Fix the build on FreeBSD 4.6.2Volker Lendecke2008-06-191-4/+5
| | | | (This used to be commit 4f50cb63e9b565ae0747127baa651a1a1874298b)
* Add transactions to the dbwrap APIVolker Lendecke2008-03-101-0/+11
| | | | | | Only filled in for tdb so far, for rbt it's pointless, and ctdb itself needs to be extended (This used to be commit 0a55e018dd68af06d84332d54148bbfb0b510b22)
* Restructure dbwrap_rbtVolker Lendecke2008-01-121-59/+127
| | | | | | | In this low-level code, play tricks to reduce the number of allocations to the possible minimum. I would not recommend this for higher-level code, but here it pays off. (This used to be commit 71b1e6ff1595fbaa8dd49b996c45541531c7e98c)
* Samba Shared Repository - branch v3-2-test updated - ↵Volker Lendecke2007-12-191-10/+8
| | | | | | | | | | | | | | | | | | initial-v3-2-unstable-716-g12cce3b On Tue, Dec 18, 2007 at 06:04:32PM -0600, Jeremy Allison wrote: > Fix valgrind error in dbwrap_rbt where rec_priv->node was > being accessed after free. VALOKER PLEASE CHECK THIS VERY > CAREFULLY !!!! This is a correct fix in that it fixes the > valgrind error, but it looks inelegant to me. I think if > I understood this code better I could craft a more subtle > fix. Still looking at it.... Thanks a lot. Fully correct. What about the attached little simplification? Volker (This used to be commit 5b72828600fb057a7aeb5f1a6fb6c23c23f28cd8)
* We've finished with the old node once we've copied theJeremy Allison2007-12-181-4/+4
| | | | | | keyval. Jeremy. (This used to be commit 39f3efbcc5fbdff1db1b12e5fc7368968f240993)
* Fix valgrind error in dbwrap_rbt where rec_priv->node wasJeremy Allison2007-12-181-1/+10
| | | | | | | | | | being accessed after free. VALOKER PLEASE CHECK THIS VERY CAREFULLY !!!! This is a correct fix in that it fixes the valgrind error, but it looks inelegant to me. I think if I understood this code better I could craft a more subtle fix. Still looking at it.... Jeremy. (This used to be commit 12cce3be2a24fd72106d747890caf6c7f29db43d)
* dbwrap_rbtVolker Lendecke2007-12-101-0/+303
This is meant as a replacement for the internal tdb. To me it seems a bit silly that for in-memory structures we do our own memory management. With this rbt based approach we can make use of the system-supplied malloc. (This used to be commit 54e5d4404619443caed32e2acff8921cdbff9ed1)