telemetry: fix connected clients count

Telemetry can only create 10 conns by default, each of which is processed
by a thread.

When a thread fails to write using socket, the thread will end directly
without reducing the total number of conns.

This will result in the machine running for a long time, and if there are
10 failures, the telemetry will be unavailable

Fixes: 2a7d0b8 ("telemetry: add upper limit on connections")
Cc: [email protected]

Signed-off-by: Shaowei Sun <[email protected]>
Acked-by: Bruce Richardson <[email protected]>
Acked-by: Ciara Power <[email protected]>
Acked-by: Chengwen Feng <[email protected]>

Author: sunaaaaaaa

.mailmap

@@ -1281,6 +1281,7 @@ Shally Verma <[email protected]> <[email protected]>
 Shannon Nelson <[email protected]>
 Shannon Zhao <[email protected]>
 Shaopeng He <[email protected]>
+Shaowei Sun <[email protected]>
 Sharmila Podury <[email protected]>
 Sharon Haroni <[email protected]>
 Shay Agroskin <[email protected]>

lib/telemetry/telemetry.c

@@ -378,8 +378,8 @@ client_handler(void *sock_id)
 			"{\"version\":\"%s\",\"pid\":%d,\"max_output_len\":%d}",
 			telemetry_version, getpid(), MAX_OUTPUT_LEN);
 	if (write(s, info_str, strlen(info_str)) < 0) {
-		close(s);
-		return NULL;
+		TMTY_LOG_LINE(ERR, "Socket write base info to client failed");
+		goto exit;
 	}
 
 	/* receive data is not null terminated */
@@ -404,6 +404,7 @@ client_handler(void *sock_id)
 
 		bytes = read(s, buffer, sizeof(buffer) - 1);
 	}
+exit:
 	close(s);
 	rte_atomic_fetch_sub_explicit(&v2_clients, 1, rte_memory_order_relaxed);
 	return NULL;