aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/timer.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2010-05-23 08:14:45 +0200
committerThomas Gleixner <tglx@linutronix.de>2010-05-24 11:50:38 +0200
commitbd45b7a385c5ffd82c11a1d51880be18559e5ad9 (patch)
treed5fb7949b599a0a0aa86233d8c3118cc5b0bf9b9 /kernel/timer.c
parentf4b87dee923342505e1ddba8d34ce9de33e75050 (diff)
downloadkernel_samsung_smdk4412-bd45b7a385c5ffd82c11a1d51880be18559e5ad9.zip
kernel_samsung_smdk4412-bd45b7a385c5ffd82c11a1d51880be18559e5ad9.tar.gz
kernel_samsung_smdk4412-bd45b7a385c5ffd82c11a1d51880be18559e5ad9.tar.bz2
timekeeping: Fix timezone update
commit 64ce4c2f (time: Clean up warp_clock()) breaks the timezone update in a very subtle way. To avoid the direct access to timekeeping internals it adds the timezone delta to the current time with timespec_add_safe(). This works nicely when the timezone delta is > 0. If timezone delta is < 0 then the wrap check in timespec_add_safe() triggers and timespec_add_safe() returns TIME_MAX and screws up timekeeping completely. The comment above timespec_add_safe() says: It's assumed that both values are valid (>= 0) Add the timezone seconds adjustment directly. Reported-by: Rafael J. Wysocki <rjw@sisk.pl> Tested-by: Rafael J. Wysocki <rjw@sisk.pl> Acked-by: John Stultz <johnstul@us.ibm.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'kernel/timer.c')
0 files changed, 0 insertions, 0 deletions