summaryrefslogtreecommitdiff
path: root/fs/ext4/bitmap.c
diff options
context:
space:
mode:
authorHeiko Carstens <heiko.carstens@de.ibm.com>2013-01-29 09:16:28 +0100
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2013-01-31 14:01:52 +0100
commitd911e03d097bdc01363df5d81c43f69432eb785c (patch)
tree874dad34e0f361cefbed2ea5fbc8f19ac3a6dccf /fs/ext4/bitmap.c
parent04c2eee5b9dfcb13f3cd07a5537fb8c785f2751a (diff)
s390/timer: avoid overflow when programming clock comparator
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function is used to avoid overflows when converting TOD format values to nanosecond values. The kvm interrupt code formerly however only worked by accident because of an overflow. It tried to program a timer that would expire in more than ~29 years. Because of the old TOD-to-nanoseconds overflow bug the real expiry value however was much smaller, but now it isn't anymore. This however triggers yet another bug in the function that programs the clock comparator s390_next_ktime(): if the absolute "expires" value is after 2042 this will result in an overflow and the programmed value is lower than the current TOD value which immediatly triggers a clock comparator (= timer) interrupt. Since the timer isn't expired it will be programmed immediately again and so on... the result is a dead system. To fix this simply program the maximum possible value if an overflow is detected. Reported-by: Christian Borntraeger <borntraeger@de.ibm.com> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com> Cc: stable@vger.kernel.org # v3.3+ Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Diffstat (limited to 'fs/ext4/bitmap.c')
0 files changed, 0 insertions, 0 deletions