summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorjohn stultz <johnstul@us.ibm.com>2009-05-01 20:10:25 (GMT)
committerThomas Gleixner <tglx@linutronix.de>2009-05-02 08:22:27 (GMT)
commit74a03b69d1b5ce00a568e142ca97e76b7f5239c6 (patch)
tree02bdea43ae6d528dcee97c00c3a8651f8841411a /fs
parent091438dd5668396328a3419abcbc6591159eb8d1 (diff)
downloadlinux-74a03b69d1b5ce00a568e142ca97e76b7f5239c6.tar.xz
clockevents: prevent endless loop in tick_handle_periodic()
tick_handle_periodic() can lock up hard when a one shot clock event device is used in combination with jiffies clocksource. Avoid an endless loop issue by requiring that a highres valid clocksource be installed before we call tick_periodic() in a loop when using ONESHOT mode. The result is we will only increment jiffies once per interrupt until a continuous hardware clocksource is available. Without this, we can run into a endless loop, where each cycle through the loop, jiffies is updated which increments time by tick_period or more (due to clock steering), which can cause the event programming to think the next event was before the newly incremented time and fail causing tick_periodic() to be called again and the whole process loops forever. [ Impact: prevent hard lock up ] Signed-off-by: John Stultz <johnstul@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@kernel.org
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions