From bd83314ee91824badaa23207188163089b7b2b22 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Tue, 8 May 2012 15:51:44 +0200 Subject: [PATCH] BUG/MEDIUM: log: ensure that unique_id is properly initialized Last memory poisonning patch immediately made this issue appear. The unique_id field is released but not properly initialized. The feature was introduced very recently, no backport is needed. --- src/peers.c | 1 + src/session.c | 1 + 2 files changed, 2 insertions(+) diff --git a/src/peers.c b/src/peers.c index 182d71d23..42018e13f 100644 --- a/src/peers.c +++ b/src/peers.c @@ -1204,6 +1204,7 @@ static struct session *peer_session_create(struct peer *peer, struct peer_sessio s->srv_error = default_srv_error; s->uniq_id = 0; + s->unique_id = NULL; txn = &s->txn; /* Those variables will be checked and freed if non-NULL in diff --git a/src/session.c b/src/session.c index 862af5853..cd02da24d 100644 --- a/src/session.c +++ b/src/session.c @@ -97,6 +97,7 @@ int session_accept(struct listener *l, int cfd, struct sockaddr_storage *addr) LIST_ADDQ(&sessions, &s->list); LIST_INIT(&s->back_refs); + s->unique_id = NULL; s->term_trace = 0; s->si[0].addr.from = *addr; s->logs.accept_date = date; /* user-visible date for logging */