A compiler warning drew my attention to the fact that 'next' in
pinger_schedule() was an int, not the unsigned long it should have
been. And looking at the code that handles it, it was also taking no
care with integer wraparound when checking whether an existing
scheduled ping should be moved forward.
So now I do something a bit more robust, by remembering what time it
_was_ when we set pinger->next, and checking if the new time value
falls in the interval between those two times.
struct pinger_tag {
int interval;
int pending;
- unsigned long next;
+ unsigned long when_set, next;
Backend *back;
void *backhandle;
};
static void pinger_schedule(Pinger pinger)
{
- int next;
+ unsigned long next;
if (!pinger->interval) {
pinger->pending = FALSE; /* cancel any pending ping */
next = schedule_timer(pinger->interval * TICKSPERSEC,
pinger_timer, pinger);
- if (!pinger->pending || next < pinger->next) {
+ if (!pinger->pending ||
+ (next - pinger->when_set) < (pinger->next - pinger->when_set)) {
pinger->next = next;
+ pinger->when_set = timing_last_clock();
pinger->pending = TRUE;
}
}
void expire_timer_context(void *ctx);
int run_timers(unsigned long now, unsigned long *next);
void timer_change_notify(unsigned long next);
+unsigned long timing_last_clock(void);
/*
* Exports from callback.c.
return when;
}
+unsigned long timing_last_clock(void)
+{
+ /*
+ * Return the last value we stored in 'now'. In particular,
+ * calling this just after schedule_timer returns the value of
+ * 'now' that was used to decide when the timer you just set would
+ * go off.
+ */
+ return now;
+}
+
/*
* Call to run any timers whose time has reached the present.
* Returns the time (in ticks) expected until the next timer after