Skip to content
Browse files

timerfd: Fix wakeup of processes when timer is cancelled on clock change

Currently processes waiting with poll on cancelable timerfd timers are
not woken up when the timers are canceled. When the system time is set
the clock_was_set() function calls timerfd_clock_was_set() to cancel
and wake up processes waiting on potential cancelable timerfd
timers. However the wake up currently has no effect because in the
case of timerfd_read it is dependent on ctx->ticks not being
0. timerfd_poll also requires ctx->ticks being non zero. As a
consequence processes waiting on cancelable timers only get woken up
when the timers expire. This patch fixes this by incrementing
ctx->ticks before calling wake_up.

Signed-off-by: Max Asbock <>
Cc: johnstul <>
Signed-off-by: Thomas Gleixner <>
  • Loading branch information...
1 parent 2c53b43 commit 1123d93963cbd2546449d4d9f0c568e323cb0ac6 Max Asbock committed with Thomas Gleixner
Showing with 4 additions and 1 deletion.
  1. +4 −1 fs/timerfd.c
5 fs/timerfd.c
@@ -61,7 +61,9 @@ static enum hrtimer_restart timerfd_tmrproc(struct hrtimer *htmr)
* Called when the clock was set to cancel the timers in the cancel
- * list.
+ * list. This will wake up processes waiting on these timers. The
+ * wake-up requires ctx->ticks to be non zero, therefore we increment
+ * it before calling wake_up_locked().
void timerfd_clock_was_set(void)
@@ -76,6 +78,7 @@ void timerfd_clock_was_set(void)
spin_lock_irqsave(&ctx->wqh.lock, flags);
if (ctx->moffs.tv64 != moffs.tv64) {
ctx->moffs.tv64 = KTIME_MAX;
+ ctx->ticks++;
spin_unlock_irqrestore(&ctx->wqh.lock, flags);

0 comments on commit 1123d93

Please sign in to comment.
Something went wrong with that request. Please try again.