api: fix rx timeout thread busy loop after reconnect
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
This commit is contained in:
Vladislav Grishenko
committed by
Ole Tr�an
parent
e53e296841
commit
b24ff24da9
@ -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) {
|
||||
|
Reference in New Issue
Block a user