From 3cc30186f9d9adb565dc29f2d4e68889974676ae Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Mon, 16 Dec 2019 12:49:07 -0800 Subject: [PATCH] Use INT_MAX instead of TIME_T_MAX for timerfd_settime timeout kernel prior to 64bit time_t support might not entertain such large timeout therefore reduce it to INT_MAX which would set timer expiration event after 68 years of uptime, should be good for all practical purposes Upstream-Status: Pending Signed-off-by: Khem Raj Upstream-Status: Pending --- src/basic/time-util.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/basic/time-util.c b/src/basic/time-util.c index d7ef30d2fe52..4d3219f114b5 100644 --- a/src/basic/time-util.c +++ b/src/basic/time-util.c @@ -1487,7 +1487,7 @@ int time_change_fd(void) { /* We only care for the cancellation event, hence we set the timeout to the latest possible value. */ static const struct itimerspec its = { - .it_value.tv_sec = TIME_T_MAX, + .it_value.tv_sec = INT_MAX, }; _cleanup_close_ int fd;