io-threads: Fix missed notification in sem_timedwait

We're performing a calculation for skewing idle time
that resulted in a timespec.tv_nsec value becoming larger than
1000 million or less than 0, forcing sem_timedwait to return
with an EINVAL instead of waiting for a request notification
from sem_post in iot_notify_worker(). This resulted in a missed
notification that resulted in a hang followed by a timeout
on the protocol/client side.

This commit avoids the over- and under-flow in tv_nsec by
skewing the tv_sec value instead.

Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

0 files changed, 0 insertions, 0 deletions