diff options
author | Maciej W. Rozycki <macro@linux-mips.org> | 2008-05-12 14:02:24 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-13 08:02:25 -0700 |
commit | 945185a69daa457c4c5e46e47f4afad7dcea734f (patch) | |
tree | 688be6d624632b5538c925ac278511ea2aa79f02 /drivers/rtc/rtc-rs5c313.c | |
parent | f38c84312748de9d04562c12af57080c6901f931 (diff) | |
download | linux-945185a69daa457c4c5e46e47f4afad7dcea734f.tar.gz linux-945185a69daa457c4c5e46e47f4afad7dcea734f.tar.bz2 linux-945185a69daa457c4c5e46e47f4afad7dcea734f.zip |
rtc: rtc_time_to_tm: use unsigned arithmetic
The input argument to rtc_time_to_tm() is unsigned as well as are members of
the output structure. However signed arithmetic is used within for
calculations leading to incorrect results for input values outside the signed
positive range. If this happens the time of day returned is out of range.
Found the problem when fiddling with the RTC and the driver where year was set
to an unexpectedly large value like 2070, e.g.:
rtc0: setting system clock to 2070-01-01 1193046:71582832:26 UTC (3155760954)
while it should be:
rtc0: setting system clock to 2070-01-01 00:15:54 UTC (3155760954)
Changing types to unsigned fixes the problem.
[akpm@linux-foundation.org: remove old-fashioned `register' keyword]
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>
Cc: David Brownell <david-b@pacbell.net>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/rtc/rtc-rs5c313.c')
0 files changed, 0 insertions, 0 deletions