samba.git/lib/talloc/talloc.c, branch talloc-2.0.7

talloc: Remove an unused variable

2011-09-07T14:47:26+00:00

Autobuild-User: Volker Lendecke 
Autobuild-Date: Wed Sep  7 16:47:26 CEST 2011 on sn-devel-104

talloc: ensure the sibling linked list remains valid during a free

2011-08-08T23:53:16+00:00

This ensures that the sibling list of a pointer doesn't become invalid
during a free operation. It is an alternative fix to the fix in
6f51a1f45bf4de062cce7a562477e8140630a53d, and avoids the problem of
trying to calculate the parent pointer early

This should fix the subtle spoolss talloc bug that Simo found

Autobuild-User: Andrew Tridgell 
Autobuild-Date: Tue Aug  9 01:53:17 CEST 2011 on sn-devel-104

talloc: preserve context name on talloc_free_children()

2011-07-29T08:17:44+00:00

Otherwise tc->name will end up pointing to garbage when it is not
set to a const but rather to a string allocate as child of the context itself.

Signed-off-by: Andrew Tridgell

talloc: splitout _talloc_free_children_internal()

2011-05-17T08:49:13+00:00

metze

Autobuild-User: Stefan Metzmacher 
Autobuild-Date: Tue May 17 10:49:13 CEST 2011 on sn-devel-104

talloc: fixed a use after free error in talloc_free_children()

2011-05-17T07:46:04+00:00

This is similar to commit 6f51a1f45bf4de062cce7a562477e8140630a53d.

metze

talloc: use _talloc_free_internal() in talloc_free_children()

2011-05-17T07:46:04+00:00

metze

talloc: setup the new 'tc' before TC_UNDEFINE_GROW_CHUNK() _talloc_realloc()

2011-05-17T06:22:23+00:00

metze

talloc: make really sure only optimize realloc if there's only one pool chunk

2011-05-17T06:22:21+00:00

*talloc_pool_objectcount(pool_tc) == 2 doesn't mean the one of the objects
is the pool itself! So we better check for == 1 and calculate the chunk count.

metze

talloc: make use of _talloc_free_poolmem() in _talloc_realloc()

2011-05-17T06:22:20+00:00

This should follow the same logic...

metze

talloc: split the handling of FLAG_POOL/FLAG_POOLMEM in _talloc_free_internal

2011-05-17T06:22:18+00:00

The optimization of the object_count == 1 case should only happen
for when we're not destroying the pool itself. And it should only
happen if the pool itself is still valid.

If the pool isn't valid (it has TALLOC_FLAG_FREE),
object_count == 1 does not mean that the pool is the last object,
which can happen if you use talloc_steal/move() on memory
from the pool and then free the pool itself.

Thanks to Volker for noticing this!

metze