diff options
author | john stultz <johnstul@us.ibm.com> | 2009-05-01 13:10:25 -0700 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2009-05-02 10:22:27 +0200 |
commit | 74a03b69d1b5ce00a568e142ca97e76b7f5239c6 (patch) | |
tree | 02bdea43ae6d528dcee97c00c3a8651f8841411a /fs/qnx4/bitmap.c | |
parent | 091438dd5668396328a3419abcbc6591159eb8d1 (diff) | |
download | op-kernel-dev-74a03b69d1b5ce00a568e142ca97e76b7f5239c6.zip op-kernel-dev-74a03b69d1b5ce00a568e142ca97e76b7f5239c6.tar.gz |
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/qnx4/bitmap.c')
0 files changed, 0 insertions, 0 deletions