s3:lsasd: Fix creating binding string for error message

Found by covscan.

Signed-off-by: Andreas Schneider <asn@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

diff --git a/source3/rpc_server/lsasd.c b/source3/rpc_server/lsasd.c
index aeeb4d7f10d6c7e8fb346e441b7764338dfbc165..2c1fc2db5d05f50d91c571862a41e24a098efb2b 100644 (file)
--- a/source3/rpc_server/lsasd.c
+++ b/source3/rpc_server/lsasd.c
@@ -576,8 +576,11 @@ static NTSTATUS lsasd_create_sockets(struct tevent_context *ev_ctx,
        for (i = 0; i < *listen_fd_size; i++) {
                rc = listen(listen_fd[i].fd, pf_lsasd_cfg.max_allowed_clients);
                if (rc == -1) {
-                       char *ep_string = dcerpc_binding_string(
-                                       dce_ctx, e->ep_description);
+                       char *ep_string = NULL;
+
+                       e = listen_fd[i].fd_data;
+                       ep_string = dcerpc_binding_string(dce_ctx,
+                                                         e->ep_description);
                        DBG_ERR("Failed to listen on endpoint '%s': %s\n",
                                ep_string, strerror(errno));
                        status = map_nt_error_from_unix(errno);