[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-51cbb5242a41700a3f250ecfb48dcfb7e4375ea4@git.kernel.org>
Date: Sun, 17 Jan 2016 02:43:47 -0800
From: tip-bot for Thomas Gleixner <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: peterz@...radead.org, hpa@...or.com, tglx@...utronix.de,
deller@....de, mingo@...nel.org, john.stultz@...aro.org,
linux-kernel@...r.kernel.org
Subject: [tip:timers/urgent] itimers:
Handle relative timers with CONFIG_TIME_LOW_RES proper
Commit-ID: 51cbb5242a41700a3f250ecfb48dcfb7e4375ea4
Gitweb: http://git.kernel.org/tip/51cbb5242a41700a3f250ecfb48dcfb7e4375ea4
Author: Thomas Gleixner <tglx@...utronix.de>
AuthorDate: Thu, 14 Jan 2016 16:54:48 +0000
Committer: Thomas Gleixner <tglx@...utronix.de>
CommitDate: Sun, 17 Jan 2016 11:13:55 +0100
itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper
As Helge reported for timerfd we have the same issue in itimers. We return
remaining time larger than the programmed relative time to user space in case
of CONFIG_TIME_LOW_RES=y. Use the proper function to adjust the extra time
added in hrtimer_start_range_ns().
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Helge Deller <deller@....de>
Cc: John Stultz <john.stultz@...aro.org>
Cc: linux-m68k@...ts.linux-m68k.org
Cc: dhowells@...hat.com
Cc: stable@...r.kernel.org
Link: http://lkml.kernel.org/r/20160114164159.528222587@linutronix.de
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
---
kernel/time/itimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/itimer.c b/kernel/time/itimer.c
index 8d262b4..1d5c720 100644
--- a/kernel/time/itimer.c
+++ b/kernel/time/itimer.c
@@ -26,7 +26,7 @@
*/
static struct timeval itimer_get_remtime(struct hrtimer *timer)
{
- ktime_t rem = hrtimer_get_remaining(timer);
+ ktime_t rem = __hrtimer_get_remaining(timer, true);
/*
* Racy but safe: if the itimer expires after the above
Powered by blists - more mailing lists