diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-11 09:36:59 +0100 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-11 10:33:33 +0100 |
| commit | 0807d1b387297ed58e498c15bddd899278104b3d (patch) | |
| tree | f03be5649323cb6c50cc1902487ce1a0d812b834 | |
| parent | 9b71be4f0b27daf3edc9ce41f13d07e305802994 (diff) | |
| download | man-pages-0807d1b387297ed58e498c15bddd899278104b3d.tar.gz | |
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>
| -rw-r--r-- | man2/timer_getoverrun.2 | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2 index e2314c1e44..5cd522d96b 100644 --- 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). |