api: fix rx timeout thread busy loop after reconnect 42/40442/2
authorVladislav Grishenko <themiron@yandex-team.ru>
Sat, 13 Mar 2021 10:17:03 +0000 (15:17 +0500)
committerOle Tr�an <otroan@employees.org>
Tue, 2 Apr 2024 06:56:37 +0000 (06:56 +0000)
After memclnt api client disconnect, read timeout is set to zero
and stays the same even after same client reconnect. It causes
client process to spin in timeout loop up to 100% cpu.
Fix it by resetting timeout process state upon every (re)connect.

Type: fix
Signed-off-by: Vladislav Grishenko <themiron@yandex-team.ru>
Change-Id: I56812972a69c343f869eebbdfebdcbefd3d201e0

src/vpp-api/client/client.c

index 7a30792..d59273e 100644 (file)
@@ -305,6 +305,8 @@ vac_connect (char * name, char * chroot_prefix, vac_callback_t cb,
   }
 
   /* Start read timeout thread */
+  timeout_in_progress = false;
+  timeout_thread_cancelled = false;
   rv = pthread_create(&pm->timeout_thread_handle, NULL,
                      vac_timeout_thread_fn, 0);
   if (rv) {