samba.git/lib/util/talloc_stack.c, branch talloc-2.4.4

lib/util: activate panic on dangling talloc stackframes

2025-05-19T09:11:29+00:00

We can do that now as pylibsmb.c doesn't trigger it anymore.

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

lib/util: add pthread support to talloc_stack.c

2025-05-19T09:11:29+00:00

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

lib/util: add atexit handling and complain about dangling frames.

2025-05-19T09:11:29+00:00

We don't panic yet as pylibsmb.c would trigger that...
This will be fixed in the next commits.

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

lib/util: remove unused SMB_THREAD handling from talloc_stack.c

2025-05-19T09:11:29+00:00

This does not support any threads as smb_thread_set_functions()
is never called anywhere.

We'll add plain pthread handling in the next commit.

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

lib: Remove an unneeded includes.h

2022-04-26T21:41:29+00:00

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

talloc_stack: Call talloc destructors while frame is still around

2018-06-23T02:56:44+00:00

This fixes "samba-tool ntacl set -d10"

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

Autobuild-User(master): Jeremy Allison 
Autobuild-Date(master): Sat Jun 23 04:56:44 CEST 2018 on sn-devel-144

talloc_stack: abort in developer me if no stackframe on talloc_tos()

2012-07-18T05:37:27+00:00

Don't tolerate leaks in developer mode.

Signed-off-by: Rusty Russell

talloc_stack: report lazy freeing (panic if DEVELOPER).

2012-07-17T19:27:31+00:00

talloc_stackframe() stacks, so if you forget to free one, the outer
one will free it.  However, it's not a good idea to rely too heavily
on this behaviour: it can lead to delays in the release of memory or
destructors.

I had an elaborate hack to make sure every talloc_stackframe() was
freed in the exact same function it was allocated, however all bugs it
caught were simply lazy freeing, so this patch just checks for that.

This doesn't check for stackframes we don't free up on exit: that would
be nice, but uncovers some uncomfortable (but probably harmless) cases.

Signed-off-by: Rusty Russell

talloc_stack: always include the location when creating a talloc_stackframe().

2012-07-17T19:26:31+00:00

Much better for debugging.

Signed-off-by: Rusty Russell

talloc_stack: handle more than one talloc_stackframe_pool()

2012-07-17T19:25:31+00:00

The only reason we make one stackframe parent of the next is so we use
our parent's pool.  That doesn't make sense if we're a new pool, and
wouldn't work anyway.

Signed-off-by: Rusty Russell