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.
diff --git a/src/peers.c b/src/peers.c
index 182d71d..42018e1 100644
--- a/src/peers.c
+++ b/src/peers.c
@@ -1204,6 +1204,7 @@
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 862af58..cd02da2 100644
--- a/src/session.c
+++ b/src/session.c
@@ -97,6 +97,7 @@
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 */