timer_getoverrun.2: timer_getoverrun() now clamps the overrun count to DELAYTIMER_MAX

See https://bugzilla.kernel.org/show_bug.cgi?id=12665.
The fix by Thomas Gleixner was in kernel commit
78c9c4dfbf8c04883941445a195276bb4bb92c76.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index e2314c1e445a081d8d330befbde935b39194e721..5cd522d96b2039515a128c300c68c14f3693e602 100644 (file)
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -121,11 +121,20 @@ then
 .BR timer_getoverrun ()
 should return
 .BR DELAYTIMER_MAX .
-However, Linux does not implement this feature: instead,
+However, before Linux 4.19,
+.\" http://bugzilla.kernel.org/show_bug.cgi?id=12665
 if the timer overrun value exceeds the maximum representable integer,
 the counter cycles, starting once more from low values.
-.\" Bug filed: http://bugzilla.kernel.org/show_bug.cgi?id=12665
-.\" http://thread.gmane.org/gmane.linux.kernel/113276/
+Since Linux 4.19,
+.\" commit 78c9c4dfbf8c04883941445a195276bb4bb92c76
+.BR timer_getoverrun ()
+returns
+.B DELAYTIMER_MAX
+(defined as
+.B INT_MAX
+in
+.IR <limits.h> )
+in this case (and the overrun value is reset to 0).
 .SH EXAMPLES
 See
 .BR timer_create (2).