summaryrefslogtreecommitdiff
path: root/source4/libcli/dgram
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2009-08-07 17:14:13 +1000
committerAndrew Tridgell <tridge@samba.org>2009-08-07 17:24:48 +1000
commite2d4ae15107c8613707adc68ffc68c6ced04e9be (patch)
treec782a84ad529555f2b635f4032605dbb1b84393c /source4/libcli/dgram
parent238bf25af44ecc51bef59f1d0b9303da9904432e (diff)
downloadsamba-e2d4ae15107c8613707adc68ffc68c6ced04e9be.tar.gz
samba-e2d4ae15107c8613707adc68ffc68c6ced04e9be.tar.bz2
samba-e2d4ae15107c8613707adc68ffc68c6ced04e9be.zip
fixed several places that unnecessarily take a reference to the event context
These references were triggering the ambiguous talloc_free errors from the recent talloc changes when the server is run using the 'standard' process model instead of the 'single' process model. I am aiming to move the build farm to use the 'standard' process model soon, as part of an effort to make our test environment better match the real deployment of Samba4. The references are not needed as the way that the event context is used is as the 'top parent', so when the event context is freed then all of the structures that were taking a reference to the event context were actually freed as well, thus making the references redundent.
Diffstat (limited to 'source4/libcli/dgram')
-rw-r--r--source4/libcli/dgram/dgramsocket.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/source4/libcli/dgram/dgramsocket.c b/source4/libcli/dgram/dgramsocket.c
index 751706d2c5..365960edb6 100644
--- a/source4/libcli/dgram/dgramsocket.c
+++ b/source4/libcli/dgram/dgramsocket.c
@@ -166,7 +166,7 @@ struct nbt_dgram_socket *nbt_dgram_socket_init(TALLOC_CTX *mem_ctx,
dgmsock = talloc(mem_ctx, struct nbt_dgram_socket);
if (dgmsock == NULL) goto failed;
- dgmsock->event_ctx = talloc_reference(dgmsock, event_ctx);
+ dgmsock->event_ctx = event_ctx;
if (dgmsock->event_ctx == NULL) goto failed;
status = socket_create("ip", SOCKET_TYPE_DGRAM, &dgmsock->sock, 0);