summaryrefslogtreecommitdiffstats
path: root/man2/timer_getoverrun.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/timer_getoverrun.2')
-rw-r--r--man2/timer_getoverrun.219
1 files changed, 14 insertions, 5 deletions
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index a0a3e50fc..f3e1d7782 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -23,7 +23,7 @@
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH TIMER_GETOVERRUN 2 2020-06-09 Linux "Linux Programmer's Manual"
+.TH TIMER_GETOVERRUN 2 2020-12-21 Linux "Linux Programmer's Manual"
.SH NAME
timer_getoverrun \- get overrun count for a POSIX per-process timer
.SH SYNOPSIS
@@ -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).
@@ -140,7 +149,7 @@ See
.BR signal (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 5.09 of the Linux
+This page is part of release 5.10 of the Linux
.I man-pages
project.
A description of the project,