r20330: And here's the fix for the parent winbindd crashing

after it's child died unexpectedly whilst the parent
was waiting for a reply. We need to clean up the request
we're not going to service, plus we still need to call
the continuation function with a "False" flag so it
can clean things up. Still testing this, but I think
I'm right.
Jeremy

diff --git a/source/nsswitch/winbindd_dual.c b/source/nsswitch/winbindd_dual.c
index fc8a95dfc0c81804b103d2f61d444e0b37ea7d76..b72b7238b1f2698374e2dbe3a066e9f55737d8c0 100644 (file)
--- a/source/nsswitch/winbindd_dual.c
+++ b/source/nsswitch/winbindd_dual.c
@@ -192,7 +192,12 @@ static void async_reply_recv(void *private_data, BOOL success)
 
        if (!success) {
                DEBUG(5, ("Could not receive async reply\n"));
+
+               cache_cleanup_response(child->pid);
+               DLIST_REMOVE(child->requests, state);
+
                state->response->result = WINBINDD_ERROR;
+               state->continuation(state->private_data, False);
                return;
        }