Tesing of / bugs in new timerfd API
Davide, Andrew,
I applied Davide's v3 patchset (sent into LKML on 25 Nov) against 2.4.24-rc3, and did various tests (all on x86). Several tests were done using the program at the foot of this mail. Various others were done by cobbling together bits of code that I haven't included here.
In covering the tests I ran, and as a kind of proof of concept, I'll treat the draft man page as the test spec.
I think I've found two bugs (look for the string "BUG" below), one of which is a significant deviation from expected behavior. See the comments below.
Cheers,
Michael
Quoted 26 lines
SYNOPSIS
#include <sys/timerfd.h> int timerfd_create(int clockid, int flags); int timerfd_settime(int fd, int flags, const struct itimerspec *new_value, struct itimerspec *curr_value); int timerfd_gettime(int fd, struct itimerspec *curr_value);DESCRIPTION
These system calls create and operate on a timer that delivers timer expiration notifications via a file descriptor. They provide an alternative to the use of setitimer(2) ortimer_create(3), with the advantage that the file descriptor may be monitored by select(2), poll(2), and epoll(7).The use of these three system calls is analogous to the use of
timer_create(3),timer_settime(3), and timer_get-
time(3). (There is no analog oftimer_gettoverrun(3),
since that functionality is provided by read(2), as described below.)
Quoted 6 lines
timerfd_create()
timerfd_create()creates a new timer object, and returns
a file descriptor that refers to that timer. The
clockid argument specifies the clock that is used to mark the progress of the timer, and must be eitherCLOCK_REALTIMEorCLOCK_MONOTONIC.
Verified. I've tried creating various combinations of CLOCK_REALTIME and CLOCK_MONOTONIC timers, both one shot (it_interval is zero) and repeating (it_interval is non-zero), and everything works as I would expect.
Quoted 9 lines
CLOCK_REALTIMEis a
settable system-wide clock.CLOCK_MONOTONICis a non- settable clock that is not affected by discontinuous changes in the system clock (e.g., manual changes to system time). The current value of each of these clocks can be retrieved usingclock_gettime(3).The flags argument is reserved for future use. As at
Linux 2.6.25, this argument must be specified as zero.
(Verified: see the ERRORS section of the man page, below.)
Quoted 3 lines
timerfd_settime()
timerfd_settime()arms (starts) or disarms (stops) the timer referred to by the file descriptor fd.
Disarming a timer works fine in my tests.
Quoted 17 lines
The
new_valueargument specifies the initial expiration and interval for the timer. The itimer structure used for this argument contains two fields, each of which is in turn a structure of type timespec:struct timespec {
time_ttv_sec; /* Seconds */
longtv_nsec; /* Nanoseconds */
};struct itimerspec {
struct timespecit_interval; /* Interval for
periodic timer */
struct timespecit_value; /* Initial
expiration */
};
Quoted 5 lines
new_value.it_value specifies the initial expiration of
the timer, in seconds and nanoseconds. Setting either
field of new_value.it_value to a non-zero value arms the timer. Setting both fields of new_value.it_value to zero disarms the timer.
Verified: setting both fields of new_value.it_value to zero disarms the timer.
Quoted 4 lines
Setting one or both fields of new_value.it_interval to non-zero values specifies the period, in seconds and nanoseconds, for repeated timer expirations after the
initial expiration.
I've tested intervals down to 1 nanosec, which seem to seems to work as I would expect. (But see the BUG reported below.)
Quoted 3 lines
If both fields of
new_value.it_interval are zero, the timer expires just once, at the time specified by new_value.it_value.
Verified.
Quoted 8 lines
The flags argument is either 0, to start a relative timer (new_value.it_interval specifies a time relative to the current value of the clock specified by clockid),
orTFD_TIMER_ABSTIME, to start an absolute timer
(new_value.it_interval specifies an absolute time for the clock specified by clockid; that is, the timer will expire when the value of that clock reaches the value specified in new_value.it_interval).
Tested: after setting a CLOCK_REALTIME timer with the TFD_TIMER_ABSTIME flag to expire at some time in the past with a non-zero interval (e.g., setting 100 seconds in the past, with a 5 second interval), read() from the file descriptor returns the correct number of expirations (e.g., 20).
This seems a reasonable thing to do, I suppose. However, while playing around to test this, I found what looks like a bug (see below).
BUG 1:
However, this test exposed what looks like a bug: if I set a CLOCK_REALTIME clock to expire in the past, with a very small interval, then the maximum number of expirations that can be returned via read seems to be limited to 32 bits, even though we have a 64-bit value for returning this information. I haven't checked the kernel source to determine where this bug is.
To demonstrate the bug use the program appended to this mail, as follows:
# The following starts a CLOCK_REALTIME repeating timer with
# an interval of 1 microsecs (1000 nanosecs), with an initial # expiration of just under 2^32 nanoseconds in the past. # The '-a' flags says use TFD_TIMER_ABSTIME for timer_settime() calls. # The 'r' command reads from the timerfd file descriptor.
$ ./timerfd_test -a -- -4290 0 0 1000 Initial setting for settime: value=1197543860.000, interval=0.000 ./timerfd_test> r <-- type this immediately Read: 4292190752 <-- nearly 2^32 expirations, as expected
$ ./timerfd_test -a -- -4290 0 0 1000 Initial setting for settime: value=1197543900.000, interval=0.000 ./timerfd_test> r <-- type this after 5 secs Read: 2992244 <-- Looks like the counter rolled over
Quoted 4 lines
The
curr_valueargument returns a structure containing the setting of the timer that was current at the time of the call; see the description oftimerfd_gettime()fol- lowing.
See the bug described under timerfd_gettime().
Quoted 11 lines
timerfd_gettime()
timerfd_gettime()returns, incurr_value, an itimerspec that contains the current setting of the timer referred to by the file descriptor fd.The
it_valuefield returns the amount of time until the timer will next expire. If both fields of this struc- ture are zero, then the timer is currently disarmed. This field always contains a relative value, regardless of whether theTFD_TIMER_ABSTIMEflag was specified when setting the timer.
BUG 2:
The last sentence does not match the implementation. (Nor is it consistent with the behavior of POSIX timers. And I *think* things did work correctly in the original timerfd() implementation, but I have not gone back to check.)
Suppose that we set an absolute timer to expire 100 seconds in the future. Then according to this sentence of the man page then each subsequent call to timerfd_gettime() should retrun an itimerspec structure whose it_value steadily decreases from 100 to 0 (when the timer expires). (This is the behavior in the analogous situation with POSIX timers and with setitimer()/getitimer().)
However, the implementation of timerfd_gettime() always returns the "time when the timer would next expire", and this value depends on whether TFD_TIMER_ABSTIME was specified when setting the timer.
Examples:
$ ./timerfd_test -a -- 100 # -a means TFD_TIMER_ABSTIME Initial setting for settime: value=1197550329.140, interval=0.000 ./timerfd_test> g <-- Calls timerfd_gettime() (elapsed time= 1) Current value: value=1197550329.140, interval=0.000
$ ./timerfd_test -- 100 Initial setting for settime: value=100.295, interval=0.000 ./timerfd_test> g (elapsed time= 2) Current value: value=18208.440, interval=0.000
In both of the above examples, the "value" retrieved by timer_gettime() should be a number <= 100.
BUG 2a:
The bug described for timerfd_gettime() also applies for the 'curr_value' returned by a call to timerfd_settime().
Quoted 1 line
The
it_intervalfield returns the interval of the timer.
Verified: the above was true in all my tests.
Quoted 3 lines
If both fields of this structure are zero, then the timer is set to expire just once, at the time specified by curr_value.it_value.
Verified.
Quoted 11 lines
Operating on a timer file descriptor
The file descriptor returned bytimerfd_create()sup- ports the following operations:read(2)
If the timer has already expired one or more times since its settings were last modified usingtimerfd_settime(), or since the last successful read(2), then the buffer given to read(2) returns an unsigned 8-byte integer (uint64_t) containing the number of expirations that have occurred.
Verified: each call to timerfd_settime() resets the "expiration count" to 0, even if a previous setting of the timer had already expired.
Quoted 7 lines
(The returned value is in host byte order, i.e., the native byte order for integers on the host machine.)
If no timer expirations have occurred at the time of the read(2), then the call either blocks until the next timer expiration,
Verified.
Quoted 4 lines
or fails with the
error EAGAIN if the file descriptor has been made non-blocking (via the use of the fcntl(2)F_SETFLoperation to set theO_NONBLOCKflag).
Verified.
Quoted 2 lines
A read(2) will fail with the error EINVAL if the size of the supplied buffer is less than 8 bytes.
Verified.
Quoted 4 lines
poll(2), select(2) (and similar)
The file descriptor is readable (the select(2) readfds argument; the poll(2) POLLIN flag) if one or more timer expirations have occurred.
Verified for both poll() and select().
Quoted 10 lines
The file descriptor also supports the other file-
descriptor multiplexing APIs: pselect(2),
ppoll(2), and epoll(7).close(2)
When the file descriptor is no longer required it
should be closed. When all file descriptors
associated with the same timer object have been closed, the timer is disarmed and its resources are freed by the kernel.
Not verified. (No easy way to do that from userspace.)
Quoted 7 lines
fork(2) semantics
After a fork(2), the child inherits a copy of the file descriptor created by timerfd_create(). The filedescriptor refers to the same underlying timer object as the corresponding file descriptor in the parent, and read(2)s in the child will return information about expirations of the timer.
Verified. Reads from a dup(2)ed file descriptor, or a file descriptor duplicated via a fork(2) can be used to read expiration information.
Quoted 4 lines
execve(2) semantics
A file descriptor created bytimerfd_create()is pre- served across execve(2), and continues to generate timer expirations if the timer was armed.
Verified. A timerfd file descriptor is preserved across an exceve(), and continues to generate timer expirations that can be read(2).
Quoted 4 lines
RETURN VALUE
On success,timerfd_create()returns a new file descrip- tor. On error, -1 is returned and errno is set to indi- cate the error.
Verified. (And obvious.)
Quoted 3 lines
timerfd_settime()andtimerfd_gettime()return 0 on suc- cess; on error they return -1, and set errno to indicate the error.
Verified. (And obvious.)
Quoted 5 lines
ERRORS
timerfd_create()can fail with the following errors:EINVAL The clockid argument is neither
CLOCK_MONOTONIC
norCLOCK_REALTIME;
(CLOCK_MONOTONIC is 1, CLOCK_REALTIME is 0)
Tested: clockid == 2, clockid == -1;
timerfd_create() fails with EINVAL, as expected.
Quoted 1 line
or flags is invalid.
Currently, 'flags' must be zero.
Tested: flags == 1;
timerfd_create() fails with EINVAL, as expected.
Quoted 2 lines
EMFILE The per-process limit of open file descriptors
has been reached.
Not tested.
Quoted 2 lines
ENFILE The system-wide limit on the total number of open
files has been reached.
Not tested.
Quoted 2 lines
ENODEV Could not mount (internal) anonymous i-node
device.
Not tested.
Quoted 2 lines
ENOMEM There was insufficient kernel memory to create
the timer.
Not tested.
Quoted 4 lines
timerfd_settime()andtimerfd_gettime()can fail with the following errors:EBADF fd is not a valid file descriptor.
Tested for timerfd_gettime() and timerfd_settime().
An invalid file descriptor (i.e., a file descriptor that is not open) yields the error EBADF, as expected.
Quoted 1 line
EINVAL fd is not a valid timerfd file descriptor.
Tested for timerfd_gettime() and timerfd_settime().
Passing a file descriptor that refers to an object other than a timerfd fails with the error EINVAL, as expected.
Quoted 3 lines
new_valueis not properly initialized (one of the
tv_nsecfalls outside the range zero to
999,999,999).
Tested for timerfd_settime().
Specifying it_value.tv_nsec == 1000000000 or
it_interval.tv_nsec == 1000000000 yields the error EINVAL,
as expected.--- END MAN PAGE TEXT ---
/* timerfd_test.c */
/* Link with -lrt */
#define _GNU_SOURCE
#include <sys/syscall.h>
#include <unistd.h>
#include <time.h>
#if defined(__i386__)
#define __NR_timerfd_create 322
#define __NR_timerfd_settime 325
#define __NR_timerfd_gettime 326
#endif
static inttimerfd_create(int clockid, int flags)
{
return syscall(__NR_timerfd_create, clockid, flags);
}static int
timerfd_settime(int fd, int flags, struct itimerspec *new_value,
struct itimerspec *curr_value)
{
return syscall(__NR_timerfd_settime, fd, flags,
new_value, curr_value);
}
static inttimerfd_gettime(int fd, struct itimerspec *curr_value)
{
return syscall(__NR_timerfd_gettime, fd, curr_value);
}#define TFD_TIMER_ABSTIME (1 << 0)
#define handle_error(msg) \
do { perror(msg); exit(EXIT_FAILURE); } while (0)
// #include <sys/timerfd.h>
#include <time.h>
#include <sys/times.h>
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <stdint.h> /* Definition of uint64_t */
static voidusage(const char *pname, const char *msg)
{
if (msg != NULL)
printf("%s", msg);
fprintf(stderr, "Usage: %s [options] value-sec [value-nsec "
"[intvl-sec [intvl-nsec]]]\n", pname);
fprintf(stderr, "Options are:\n");
fprintf(stderr, "\t-a Use absolute timer\n");
fprintf(stderr, "\t-m Use CLOCK_MONOTONIC "
"(instead of CLOCK_REALTIME)\n");
exit(EXIT_FAILURE);
} /* usage */static voiddisplay_help(void)
{
printf("n val-sec val-nsec intvl-sec intvl-nsec\n"
" Reset timer value & interval\n");
printf("g Get timer value\n");
printf("r Read from file descriptor\n");
printf("t Print elapsed time\n");
} /* display_help */#define MAX_LINE 1024
static voidprint_itimerspec(struct itimerspec *its)
{
printf("value=%ld.%03ld, interval=%ld.%03ld",
(long) its->it_value.tv_sec,
(long) its->it_value.tv_nsec / 1000000,
(long) its->it_interval.tv_sec,
(long) its->it_interval.tv_nsec / 1000000);
} /* print_itimerspec */intmain(int argc, char *argv[])
{
struct itimerspec new_value, curr_value;
int fd, flags;
struct timespec now;
int s, opt, use_abs_timer, use_monotonic;
long arg1, arg2, arg3, arg4;
uint64_t exp;
time_t start;
char line[MAX_LINE];
int num_read, clockid;
char cmd;
use_abs_timer = 0;
use_monotonic = 0;
while ((opt = getopt(argc, argv, "am")) != -1) {
switch (opt) {
case 'a':
use_abs_timer = 1;
break;
case 'm':
use_monotonic = 1;
break;
default:
usage(argv[1], NULL);
break;
} /* switch */
} /* while */
clockid = (use_monotonic ? CLOCK_MONOTONIC : CLOCK_REALTIME);
if (optind + 1 > argc)
usage(argv[0], NULL);
if (clock_gettime(clockid, &now) == -1)
handle_error("clock_gettime");
flags = use_abs_timer ? TFD_TIMER_ABSTIME : 0;
/* Create a timer with initial expiration and interval
as specified in command line */
if (use_abs_timer) {
new_value.it_value.tv_sec = now.tv_sec + atoi(argv[optind]);
new_value.it_value.tv_nsec = (argc > optind + 1) ?
atol(argv[optind + 1]) : now.tv_nsec;
} else {
new_value.it_value.tv_sec = atoi(argv[optind]);
new_value.it_value.tv_nsec = (argc > optind + 1) ?
atol(argv[optind + 1]) : now.tv_nsec;
}
new_value.it_interval.tv_sec = (argc > optind + 2) ?
atol(argv[optind + 2]) : 0;
new_value.it_interval.tv_nsec = (argc > optind + 3) ?
atol(argv[optind + 3]) : 0;
fd = timerfd_create(clockid, 0);
if (fd == -1)
handle_error("timerfd_create");
printf("Initial setting for settime: ");
print_itimerspec(&new_value);
printf("\n");
s = timerfd_settime(fd, flags, &new_value, &curr_value);
if (s == -1)
handle_error("timerfd_settime");
start = time(NULL);
for ( ; ; ) {
printf("%s> ", argv[0]);
fflush(stdout);
if (fgets(line, MAX_LINE, stdin) == NULL) /* EOF */
exit(EXIT_SUCCESS);
line[strlen(line) - 1] = '\0'; /* Remove trailing '\n' */
if (*line == '\0')
continue; /* Skip blank lines */
if (line[0] == '?')
display_help();
num_read = sscanf(line, " %c %ld %ld %ld %ld",
&cmd, &arg1, &arg2, &arg3, &arg4);
switch (cmd) {
case 'n':
if (num_read != 5) {
printf("Wrong number of arguments\n");
continue;
}
if (use_abs_timer) {
printf("This is an absolute timer\n");
if (clock_gettime(clockid, &now) == -1)
handle_error("clock_gettime");
printf("Now: ");
printf("value=%ld.%03ld", (long) now.tv_sec,
(long) now.tv_nsec / 1000000);
printf("\n");
new_value.it_value.tv_sec = now.tv_sec + arg1;
new_value.it_value.tv_nsec = now.tv_nsec + arg2;
} else {
printf("This is a relative timer\n");
new_value.it_value.tv_sec = arg1;
new_value.it_value.tv_nsec = arg2;
}
new_value.it_interval.tv_sec = arg3;
new_value.it_interval.tv_nsec = arg4;
printf("New setting for settime: ");
print_itimerspec(&new_value);
printf("\n");
s = timerfd_settime(fd, flags, &new_value, &curr_value);
if (s == -1) {
perror("timerfd_settime");
break;
}
printf("Previous setting from settime: ");
print_itimerspec(&curr_value);
printf("\n");
break;
case 't':
printf("%ld\n", (long) (time(NULL) - start));
break;
case 'g':
s = timerfd_gettime(fd, &curr_value);
if (s == -1)
handle_error("timerfd_gettime");
printf("(elapsed time=%3ld)\n", (long) (time(NULL) - start));
printf("Current value: ");
print_itimerspec(&curr_value);
printf("\n");
break;
case 'r':
s = read(fd, &exp, sizeof(uint64_t));
if (s != sizeof(uint64_t))
handle_error("read");
printf("Read: %lld\n", exp);
break;
} /* switch */
} /* for */
exit(EXIT_SUCCESS);
}Quoted 7 lines · Michael Kerrisk
Davide, Andrew,
I applied Davide's v3 patchset (sent into LKML on 25 Nov) against 2.4.24-rc3, and did various tests (all on x86). Several tests were done using the program at the foot of this mail. Various others were done by cobbling together bits of code that I haven't included here.
Thanks for such a thorough test Michael.
Quoted 10 lines
Tested: after setting a
CLOCK_REALTIMEtimer with theTFD_TIMER_ABSTIMEflag to expire at some time in the past with a non-zero interval (e.g., setting 100 seconds in the past, with a 5 second interval),read()from the file descriptor returns the correct number of expirations (e.g., 20).This seems a reasonable thing to do, I suppose. However, while playing around to test this, I found what looks like a bug (see below).
Quoted 8 lines
BUG 1:
However, this test exposed what looks like a bug: if I set aCLOCK_REALTIMEclock to expire in the past, with a very small interval, then the maximum number of expirations that can be returned via read seems to be limited to 32 bits, even though we have a 64-bit value for returning this information. I haven't checked the kernel source to determine where this bug is.
Yes, true. Right now hrtimer_forward() (that we use to get the "missed" ticks) returns an unsigned long, that on 32 bit is (duh!) 32 bit :) But hrtimer_forward() has all in place to just return an u64. So, Thomas, would it be OK to have hrtimer_forward() (and the new hrtimer_forward_now()) to return a u64?
Quoted 14 lines
BUG 2:
The last sentence does not match the implementation. (Nor is it consistent with the behavior of POSIX timers. And I *think* things did work correctly in the originaltimerfd()implementation, but I have not gone back to check.)Suppose that we set an absolute timer to expire 100 seconds in the future. Then according to this sentence of the man page then each subsequent call to
timerfd_gettime()should retrun an itimerspec structure whoseit_valuesteadily decreases from 100 to 0 (when the timer expires). (This is the behavior in the analogous situation with POSIX timers and with setitimer()/getitimer().)
Quoted 4 lines
However, the implementation of
timerfd_gettime()always returns the "time when the timer would next expire", and this value depends on whetherTFD_TIMER_ABSTIMEwas specified when setting the timer.
This is been like that from the beginning of the new API. So no, the previous was behaving exactly the same WRT this feature. Is this something really needed?
- Davide
Hi Davide,
Quoted 11 lines · Davide Libenzi
Quoted 7 lines · Michael Kerrisk
Davide, Andrew,
I applied Davide's v3 patchset (sent into LKML on 25 Nov) against 2.4.24-rc3, and did various tests (all on x86). Several tests were done using the program at the foot of this mail. Various others were done by cobbling together bits of code that I haven't included here.
Thanks for such a thorough test Michael.
You're welcome!
[...]
Quoted 14 lines
Quoted 14 lines
BUG 2:
The last sentence does not match the implementation. (Nor is it consistent with the behavior of POSIX timers. And I *think* things did work correctly in the originaltimerfd()implementation, but I have not gone back to check.)Suppose that we set an absolute timer to expire 100 seconds in the future. Then according to this sentence of the man page then each subsequent call to
timerfd_gettime()should retrun an itimerspec structure whoseit_valuesteadily decreases from 100 to 0 (when the timer expires). (This is the behavior in the analogous situation with POSIX timers and with setitimer()/getitimer().)
Quoted 8 lines
Quoted 4 lines
However, the implementation of
timerfd_gettime()always returns the "time when the timer would next expire", and this value depends on whetherTFD_TIMER_ABSTIMEwas specified when setting the timer.This is been like that from the beginning of the new API. So no, the previous was behaving exactly the same WRT this feature. Is this something really needed?
Three reasons that I think of off the top of my head (and there might well be more reasosn) why this should change:
a) consistency with the other two timer APIs (POSIX timers (timer_create(), etc.), and setitimer()/getitimer()).
b) Returning the amount of time until the next expiration is more useful to userland: I'd say the most common case is for userland to want to know how long until the next expiration occurs, or to adjust that time by adding/subtracting some value to the existing setting. That is difficult to with the current implementation: the userland app must use timer_gettime(), call clock_gettime(), and calculate the difference between the two, in order to know how much time remains until the next timer expiration.
c) Currently, the information returned differs depending on whether TFD_TIMER_ABSTIME is specified -- this is not the case for the analogous situation for POSIX timers. For POSIX timers, the returned setting is always the amount of time until the timer next expires. This inconsistency is messy for applications -- the application may not (be able to) know whether or not the timer it is examining was set using TFD_TIMER_ABSTIME (the timerfd might have been created by a library, for example).
Cheers,
Michael
Signature · 3 lines
Michael Kerrisk Maintainer of the Linux man-pages project http://www.kernel.org/doc/man-pages/
Quoted 29 lines · Michael Kerrisk
Quoted 14 lines
Quoted 14 lines
BUG 2:
The last sentence does not match the implementation. (Nor is it consistent with the behavior of POSIX timers. And I *think* things did work correctly in the originaltimerfd()implementation, but I have not gone back to check.)Suppose that we set an absolute timer to expire 100 seconds in the future. Then according to this sentence of the man page then each subsequent call to
timerfd_gettime()should retrun an itimerspec structure whoseit_valuesteadily decreases from 100 to 0 (when the timer expires). (This is the behavior in the analogous situation with POSIX timers and with setitimer()/getitimer().)Quoted 8 lines
Quoted 4 lines
However, the implementation of
timerfd_gettime()always returns the "time when the timer would next expire", and this value depends on whetherTFD_TIMER_ABSTIMEwas specified when setting the timer.This is been like that from the beginning of the new API. So no, the previous was behaving exactly the same WRT this feature. Is this something really needed?
Three reasons that I think of off the top of my head (and there might well be more reasosn) why this should change:
a) consistency with the other two timer APIs (POSIX timers (
timer_create(), etc.), and setitimer()/getitimer()).
Quoted 8 lines
b) Returning the amount of time until the next expiration is more useful to userland: I'd say the most common case is for userland to want to know how long until the next expiration occurs, or to adjust that time by adding/subtracting some value to the existing setting. That is difficult to with the current implementation: the userland app must use
timer_gettime(), callclock_gettime(), and calculate the difference between the two, in order to know how much time remains until the next timer expiration.
Bah, I don't want to argue with that because otherwise it starts going towards the "typical" use cases listing, that can be found the same exact reasons to have one or the other way. And we end up wasting lots of time. We'd just have to move another thing that userspace could do, inside the kernel (subtract the current value returned by hrtimer_forward() in ->expires with "now").
Quoted 8 lines
c) Currently, the information returned differs depending on whether
TFD_TIMER_ABSTIMEis specified -- this is not the case for the analogous situation for POSIX timers. For POSIX timers, the returned setting is always the amount of time until the timer next expires. This inconsistency is messy for applications -- the application may not (be able to) know whether or not the timer it is examining was set usingTFD_TIMER_ABSTIME(the timerfd might have been created by a library, for example).
Hmm... the time returned is always the next absolute time when the next timer tick will go off. It does not depend on TFD_TIMER_ABSTIME. I return the ->expires field of the timer, and hrtimer_forward() sets it to the next absolute time.
- Davide
Hi Davide,
Quoted 20 lines · Davide Libenzi
Quoted 18 lines · Michael Kerrisk
Quoted 18 lines
Quoted 18 lines
BUG 2:
The last sentence does not match the implementation. (Nor is it consistent with the behavior of POSIX timers. And I *think* things did work correctly in the originaltimerfd()implementation, but I have not gone back to check.)Suppose that we set an absolute timer to expire 100 seconds in the future. Then according to this sentence of the man page then each subsequent call to
timerfd_gettime()should retrun an itimerspec structure whoseit_valuesteadily decreases from 100 to 0 (when the timer expires). (This is the behavior in the analogous situation with POSIX timers and with setitimer()/getitimer().)However, the implementation of
timerfd_gettime()always returns the "time when the timer would next expire", and this value depends on whetherTFD_TIMER_ABSTIMEwas specified when setting the timer.
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
This is been like that from the beginning of the new API. So no, the previous was behaving exactly the same WRT this feature. Is this something really needed?
Three reasons that I think of off the top of my head (and there might well be more reasosn) why this should change:
a) consistency with the other two timer APIs (POSIX timers (
timer_create(), etc.), and setitimer()/getitimer()).
You made no comment on this, which is perhaps the most important of the reasons to make the change.
Quoted 9 lines
Quoted 8 lines
b) Returning the amount of time until the next expiration is more useful to userland: I'd say the most common case is for userland to want to know how long until the next expiration occurs, or to adjust that time by adding/subtracting some value to the existing setting. That is difficult to with the current implementation: the userland app must use
timer_gettime(), callclock_gettime(), and calculate the difference between the two, in order to know how much time remains until the next timer expiration.
Quoted 6 lines
Bah, I don't want to argue with that because otherwise it starts going towards the "typical" use cases listing, that can be found the same exact reasons to have one or the other way. And we end up wasting lots of time. We'd just have to move another thing that userspace could do, inside the kernel (subtract the current value returned by
hrtimer_forward()in ->expires with "now").
Okay -- I still think this reason matters, but let's leave it for the moment. I think the other reasons are strong enough anyway...
Quoted 9 lines
Quoted 8 lines
c) Currently, the information returned differs depending on whether
TFD_TIMER_ABSTIMEis specified -- this is not the case for the analogous situation for POSIX timers. For POSIX timers, the returned setting is always the amount of time until the timer next expires. This inconsistency is messy for applications -- the application may not (be able to) know whether or not the timer it is examining was set usingTFD_TIMER_ABSTIME(the timerfd might have been created by a library, for example).
Quoted 4 lines
Hmm... the time returned is always the next absolute time when the next timer tick will go off. It does not depend on
TFD_TIMER_ABSTIME. I return the ->expires field of the timer, andhrtimer_forward()sets it to the next absolute time.
You snipped my example that demonstrated the problem. Both of the following runs create a timer that expires 10 seconds from "now", but observe the difference in the value returned by timerfd_gettime():
$ ./timerfd_test 10 # does not use TFD_TIMER_ABSTIME Initial setting for settime: value=10.000, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=346.448, interval=0.000
$ ./timerfd_test -a 10 # uses TFD_TIMER_ABSTIME Initial setting for settime: value=1197630855.254, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=1197630855.254, interval=0.000
Either there's an inconsistency here depending on the use of TFD_TIMER_ABSTIME, or there is a bug in my understanding or my test program (but so far I haven't spotted that bug ;-).).
Cheers,
Michael
PS There was a little bug in my test program, do do with the treatment of nanosecond command-line arguments. It didn't affect any of the tests, but for completeness, the revised version of the program is below.
/* timerfd_test.c */
/* Link with -lrt */
#define _GNU_SOURCE
#include <sys/syscall.h>
#include <unistd.h>
#include <time.h>
#if defined(__i386__)
#define __NR_timerfd_create 322
#define __NR_timerfd_settime 325
#define __NR_timerfd_gettime 326
#endif
static inttimerfd_create(int clockid, int flags)
{
return syscall(__NR_timerfd_create, clockid, flags);
}static int
timerfd_settime(int fd, int flags, struct itimerspec *new_value,
struct itimerspec *curr_value)
{
return syscall(__NR_timerfd_settime, fd, flags,
new_value, curr_value);
}
static inttimerfd_gettime(int fd, struct itimerspec *curr_value)
{
return syscall(__NR_timerfd_gettime, fd, curr_value);
}#define TFD_TIMER_ABSTIME (1 << 0)
#define handle_error(msg) \
do { perror(msg); exit(EXIT_FAILURE); } while (0)
// #include <sys/timerfd.h>
#include <time.h>
#include <sys/times.h>
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <stdint.h> /* Definition of uint64_t */
static voidusage(const char *pname, const char *msg)
{
if (msg != NULL)
printf("%s", msg);
fprintf(stderr, "Usage: %s [options] value-sec [value-nsec "
"[intvl-sec [intvl-nsec]]]\n", pname);
fprintf(stderr, "Options are:\n");
fprintf(stderr, "\t-a Use absolute timer\n");
fprintf(stderr, "\t-m Use CLOCK_MONOTONIC "
"(instead of CLOCK_REALTIME)\n");
exit(EXIT_FAILURE);
} /* usage */static voiddisplay_help(void)
{
printf("n val-sec val-nsec intvl-sec intvl-nsec\n"
" Reset timer value & interval\n");
printf("g Get timer value\n");
printf("r Read from file descriptor\n");
printf("t Print elapsed time\n");
} /* display_help */#define MAX_LINE 1024
static voidprint_itimerspec(struct itimerspec *its)
{
printf("value=%ld.%03ld, interval=%ld.%03ld",
(long) its->it_value.tv_sec,
(long) its->it_value.tv_nsec / 1000000,
(long) its->it_interval.tv_sec,
(long) its->it_interval.tv_nsec / 1000000);
} /* print_itimerspec */intmain(int argc, char *argv[])
{
struct itimerspec new_value, curr_value;
int fd, flags;
struct timespec now;
int s, opt, use_abs_timer, use_monotonic;
long arg1, arg2, arg3, arg4;
uint64_t exp;
time_t start;
char line[MAX_LINE];
int num_read, clockid;
char cmd;
use_abs_timer = 0;
use_monotonic = 0;
while ((opt = getopt(argc, argv, "am")) != -1) {
switch (opt) {
case 'a':
use_abs_timer = 1;
break;
case 'm':
use_monotonic = 1;
break;
default:
usage(argv[1], NULL);
break;
} /* switch */
} /* while */
clockid = (use_monotonic ? CLOCK_MONOTONIC : CLOCK_REALTIME);
if (optind + 1 > argc)
usage(argv[0], NULL);
if (clock_gettime(clockid, &now) == -1)
handle_error("clock_gettime");
flags = use_abs_timer ? TFD_TIMER_ABSTIME : 0;
/* Create a timer with initial expiration and interval
as specified in command line */
if (use_abs_timer) {
new_value.it_value.tv_sec = now.tv_sec + atoi(argv[optind]);
new_value.it_value.tv_nsec = (argc > optind + 1) ?
atol(argv[optind + 1]) + now.tv_nsec : now.tv_nsec;
if (new_value.it_value.tv_nsec > 1000000000) {
new_value.it_value.tv_sec +=
new_value.it_value.tv_nsec / 1000000000;
new_value.it_value.tv_nsec %= 1000000000;
} /* if */
} else {
new_value.it_value.tv_sec = atoi(argv[optind]);
new_value.it_value.tv_nsec = (argc > optind + 1) ?
atol(argv[optind + 1]) : 0;
}
new_value.it_interval.tv_sec = (argc > optind + 2) ?
atol(argv[optind + 2]) : 0;
new_value.it_interval.tv_nsec = (argc > optind + 3) ?
atol(argv[optind + 3]) : 0;
fd = timerfd_create(clockid, 0);
if (fd == -1)
handle_error("timerfd_create");
printf("Initial setting for settime: ");
print_itimerspec(&new_value);
printf("\n");
s = timerfd_settime(fd, flags, &new_value, &curr_value);
if (s == -1)
handle_error("timerfd_settime");
start = time(NULL);
for ( ; ; ) {
printf("%s> ", argv[0]);
fflush(stdout);
if (fgets(line, MAX_LINE, stdin) == NULL) /* EOF */
exit(EXIT_SUCCESS);
line[strlen(line) - 1] = '\0'; /* Remove trailing '\n' */
if (*line == '\0')
continue; /* Skip blank lines */
if (line[0] == '?')
display_help();
num_read = sscanf(line, " %c %ld %ld %ld %ld",
&cmd, &arg1, &arg2, &arg3, &arg4);
switch (cmd) {
case 'n':
if (num_read != 5) {
printf("Wrong number of arguments\n");
continue;
}
if (use_abs_timer) {
printf("This is an absolute timer\n");
if (clock_gettime(clockid, &now) == -1)
handle_error("clock_gettime");
printf("Now: ");
printf("value=%ld.%03ld", (long) now.tv_sec,
(long) now.tv_nsec / 1000000);
printf("\n");
new_value.it_value.tv_sec = now.tv_sec + arg1;
new_value.it_value.tv_nsec = now.tv_nsec + arg2;
} else {
printf("This is a relative timer\n");
new_value.it_value.tv_sec = arg1;
new_value.it_value.tv_nsec = arg2;
}
new_value.it_interval.tv_sec = arg3;
new_value.it_interval.tv_nsec = arg4;
printf("New setting for settime: ");
print_itimerspec(&new_value);
printf("\n");
s = timerfd_settime(fd, flags, &new_value, &curr_value);
if (s == -1) {
perror("timerfd_settime");
break;
}
printf("Previous setting from settime: ");
print_itimerspec(&curr_value);
printf("\n");
break;
case 't':
printf("%ld\n", (long) (time(NULL) - start));
break;
case 'g':
s = timerfd_gettime(fd, &curr_value);
if (s == -1)
handle_error("timerfd_gettime");
printf("(elapsed time=%3ld)\n", (long) (time(NULL) - start));
printf("Current value: ");
print_itimerspec(&curr_value);
printf("\n");
break;
case 'r':
s = read(fd, &exp, sizeof(uint64_t));
if (s != sizeof(uint64_t))
handle_error("read");
printf("Read: %lld\n", exp);
break;
} /* switch */
} /* for */
exit(EXIT_SUCCESS);
}Quoted 16 lines · Michael Kerrisk
You snipped my example that demonstrated the problem. Both of the following runs create a timer that expires 10 seconds from "now", but observe the difference in the value returned by
timerfd_gettime():$ ./timerfd_test 10 # does not use TFD_TIMER_ABSTIME Initial setting for settime: value=10.000, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=346.448, interval=0.000$ ./timerfd_test -a 10 # uses TFD_TIMER_ABSTIME Initial setting for settime: value=1197630855.254, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=1197630855.254, interval=0.000
Quoted 3 lines
Either there's an inconsistency here depending on the use of
TFD_TIMER_ABSTIME, or there is a bug in my understanding or my test program (but so far I haven't spotted that bug ;-).).
Can you try the two patches below? I tried them on my 32 bit box (one of the rare beasts still lingering around here) and it seems to be working fine (those go on top of the previous ones).
This fixed the 32 bit tick-count truncation, and makes the time returned to be the remaining time till the next expiration.
- Davide
--- fs/timerfd.c | 6 +++--- include/linux/hrtimer.h | 10 +++++----- kernel/hrtimer.c | 9 ++++----- kernel/posix-timers.c | 9 +++++---- 4 files changed, 17 insertions(+), 17 deletions(-)
include/linux/hrtimer.h +5 -5
@@ -295,12 +295,12 @@ }/* Forward a hrtimer so it expires after now: */ -extern unsigned long +extern u64 hrtimer_forward (struct hrtimer *timer,ktime_t now,ktime_t interval);/* Forward a hrtimer so it expires after the hrtimer's current now */ -static inline unsigned long hrtimer_forward_now (struct hrtimer *timer, -ktime_t interval) +static inline u64 hrtimer_forward_now (struct hrtimer *timer, +ktime_t interval) {return hrtimer_forward (timer, timer->base->get_time (), interval); }
@@ -322,9 +322,9 @@extern void __init hrtimers_init (void );#if BITS_PER_LONG <64 -extern unsigned long ktime_divns (const ktime_t kt,s64 div); +extern u64 ktime_divns (const ktime_t kt,s64 div);#else /* BITS_PER_LONG < 64 */ -# define ktime_divns (kt, div) (unsigned long)((kt).tv64 / (div)) +# define ktime_divns (kt, div) (u64)((kt).tv64 / (div))#endif /* Show pending timers: */
kernel/hrtimer.c +4 -5
@@ -306,7 +306,7 @@/* * Divide a ktime value by a nanosecond value */ -unsigned long ktime_divns (const ktime_t kt,s64 div) +u64 ktime_divns (const ktime_t kt,s64 div) {u64 dclc, inc, dns;int sft =0 ;
@@ -321,7 +321,7 @@ dclc >>= sft;do_div (dclc, (unsigned long ) div); - return (unsigned long) dclc; + return dclc; }#endif /* BITS_PER_LONG >= 64 */
@@ -655,10 +655,9 @@* Forward the timer expiry so it will expire in the future. * Returns the number of overruns. */ -unsigned long -hrtimer_forward (struct hrtimer *timer,ktime_t now,ktime_t interval) +u64 hrtimer_forward (struct hrtimer *timer,ktime_t now,ktime_t interval) { -unsigned long orun =1 ; +u64 orun =1 ;ktime_t delta; delta =ktime_sub (now, timer->expires);
kernel/posix-timers.c +5 -4
@@ -256,8 +256,9 @@if (timr->it.real.interval.tv64 ==0 )return ; - timr->it_overrun +=hrtimer_forward (timer, timer->base->get_time (), - timr->it.real.interval); + timr->it_overrun += (unsigned int )hrtimer_forward (timer, + timer->base->get_time (), + timr->it.real.interval); timr->it_overrun_last = timr->it_overrun; timr->it_overrun =-1 ;
@@ -386,7 +387,7 @@ now = ktime_add(now, kj); }#endif - timr->it_overrun += + timr->it_overrun += (unsigned int )hrtimer_forward (timer, now, timr->it.real.interval); ret =HRTIMER_RESTART ;
@@ -662,7 +663,7 @@*/ if (iv.tv64 && (timr->it_requeue_pending &REQUEUE_PENDING || (timr->it_sigev_notify & ~SIGEV_THREAD_ID ) ==SIGEV_NONE )) - timr->it_overrun +=hrtimer_forward (timer, now, iv); + timr->it_overrun += (unsigned int )hrtimer_forward (timer, now, iv); remaining =ktime_sub (timer->expires, now);/* Return 0 only, when the timer is expired and not pending */
fs/timerfd.c +3 -3
@@ -134,8 +134,8 @@* callback to avoid DoS attacks specifying a very * short timer period. */ - ticks += (u64 )hrtimer_forward_now (&ctx->tmr, - ctx->tintv) -1 ; + ticks +=hrtimer_forward_now (&ctx->tmr, + ctx->tintv) -1 ;hrtimer_restart (&ctx->tmr); } ctx->expired =0 ;
@@ -270,7 +270,7 @@spin_lock_irq (&ctx->wqh.lock);if (ctx->expired && ctx->tintv.tv64) { ctx->expired =0 ; - ctx->ticks += (u64 ) + ctx->ticks +=hrtimer_forward_now (&ctx->tmr, ctx->tintv) -1 ;hrtimer_restart (&ctx->tmr); }
--- fs/timerfd.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
fs/timerfd.c +11 -2
@@ -49,6 +49,15 @@return HRTIMER_NORESTART ; } +static ktime_t timerfd_get_remaining (struct timerfd_ctx *ctx) { +ktime_t now, remaining; + + now = ctx->tmr.base->get_time (); + remaining =ktime_sub (ctx->tmr.expires, now); + +return remaining.tv64 <0 ?ktime_set (0 ,0 ): remaining; +} +static void timerfd_setup (struct timerfd_ctx *ctx,int flags,const struct itimerspec *ktmr) {
@@ -240,7 +249,7 @@if (ctx->expired && ctx->tintv.tv64)hrtimer_forward_now (&ctx->tmr, ctx->tintv); - kotmr.it_value =ktime_to_timespec (ctx->tmr.expires); + kotmr.it_value =ktime_to_timespec (timerfd_get_remaining (ctx)); kotmr.it_interval =ktime_to_timespec (ctx->tintv);/*
@@ -274,7 +283,7 @@hrtimer_forward_now (&ctx->tmr, ctx->tintv) -1 ;hrtimer_restart (&ctx->tmr); } - kotmr.it_value =ktime_to_timespec (ctx->tmr.expires); + kotmr.it_value =ktime_to_timespec (timerfd_get_remaining (ctx)); kotmr.it_interval =ktime_to_timespec (ctx->tintv);spin_unlock_irq (&ctx->wqh.lock);fput (file);
Hi Davide,
Quoted 18 lines · Davide Libenzi
Quoted 16 lines · Michael Kerrisk
You snipped my example that demonstrated the problem. Both of the following runs create a timer that expires 10 seconds from "now", but observe the difference in the value returned by
timerfd_gettime():$ ./timerfd_test 10 # does not use TFD_TIMER_ABSTIME Initial setting for settime: value=10.000, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=346.448, interval=0.000$ ./timerfd_test -a 10 # uses TFD_TIMER_ABSTIME Initial setting for settime: value=1197630855.254, interval=0.000 ./timerfd_test> g (elapsed time= 1) Current value: value=1197630855.254, interval=0.000
Quoted 8 lines
Quoted 2 lines
Either there's an inconsistency here depending on the use of
TFD_TIMER_ABSTIME, or there is a bug in my understanding or my testprogram
Quoted 1 line
(but so far I haven't spotted that bug ;-).).
Can you try the two patches below? I tried them on my 32 bit box (one of the rare beasts still lingering around here) and it seems to be working fine (those go on top of the previous ones).
Against 2.6.24-rc5, I applied first your earlier patches ("v3") and then the newest patch. My tests confirm that:
Quoted 2 lines
This fixed the 32 bit tick-count truncation, and makes the time returned to be the remaining time till the next expiration.
Are you going to resubmit a new patch set that includes these latest changes?
Michael
Quoted 11 lines · Michael Kerrisk
Quoted 3 lines
Can you try the two patches below? I tried them on my 32 bit box (one of the rare beasts still lingering around here) and it seems to be working fine (those go on top of the previous ones).
Against 2.6.24-rc5, I applied first your earlier patches ("v3") and then the newest patch. My tests confirm that:
Quoted 2 lines
This fixed the 32 bit tick-count truncation, and makes the time returned to be the remaining time till the next expiration.
Are you going to resubmit a new patch set that includes these latest changes?
Yes, I'll send them out to Andrew today.
- Davide