Ronnie Sahlberg d53424731f in ctdb_call_local() we can not talloc_steal() the returned data and hang it off ctdb. ... This can cause a memory leak if the call is terminated before we have managed to respond to the client. (and the call is talloc_free()d but the data is still hanging off ctdb) instead we must talloc_steal() the data and hang it off the call structure to avoid the memory leak. In order to do this we must also change the call structure that is passed into ctdb_call_local() to be allocated through talloc(). This structure was previously either a static variable, or an element of a larger talloc()ed structure (ctdb_call_state or ctdb_client_call_state) so we must change all creations of a ctdb_call into explicitely creating it through talloc() (This used to be ctdb commit 4becf32aea088a25686e8bc330eb47d85ae0ef8f)		2008-03-19 13:54:17 +11:00
..
cmdline.h	moved cmdline.c to common code	2007-04-17 22:16:50 +10:00
ctdb_private.h	in ctdb_call_local() we can not talloc_steal() the returned data and hang it off ctdb.	2008-03-19 13:54:17 +11:00
ctdb.h	add a new file <reclock>.pnn where each recovery daemon can lock that byte at offset==pnn to offer an alternative way to detect which nodes are active instead of relying on CONNECTED being accurate.	2008-02-29 12:37:42 +11:00
idtree.h	- added in idtree for efficient reqid handling	2006-11-28 20:48:34 +11:00
includes.h	added debug constants to allow for better mapping to syslog levels	2008-02-04 17:44:24 +11:00