From: Arnd Bergmann <arnd@arndb.de>
To: Xunlei Pang <xlpang@126.com>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
John Stultz <john.stultz@linaro.org>,
Xunlei Pang <pang.xunlei@linaro.org>,
Herbert Valerio Riedel <hvr@gnu.org>
Subject: Re: [PATCH RESEND 2/3] drivers/rtc/isl1208: Replace deprecated rtc_tm_to_time()
Date: Mon, 01 Jun 2015 21:49:24 +0200 [thread overview]
Message-ID: <2324798.u1fgEdZHfl@wuerfel> (raw)
In-Reply-To: <1432911877-607-2-git-send-email-xlpang@126.com>
On Friday 29 May 2015 23:04:36 Xunlei Pang wrote:
> From: Xunlei Pang <pang.xunlei@linaro.org>
>
> isl1208_i2c_set_alarm() uses deprecated rtc_tm_to_time(),
> which will overflow in year 2106 on 32-bit machines.
>
> This patch solves this by:
> - Replacing rtc_tm_to_time() with rtc_tm_to_time64()
>
> Cc: Herbert Valerio Riedel <hvr@gnu.org>
> Signed-off-by: Xunlei Pang <pang.xunlei@linaro.org>
> ---
> drivers/rtc/rtc-isl1208.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
The patch looks correct, but I wonder if this is the best solution.
The only use of the two time values in the function is in the
'alarm_secs <= rtc_secs' comparison.
Maybe we should introduce an 'rtc_tm_before' helper function that
performs the same check? Do other drivers use the same piece
of code as this one?
Arnd
> diff --git a/drivers/rtc/rtc-isl1208.c b/drivers/rtc/rtc-isl1208.c
> index c3c549d..06113e8 100644
> --- a/drivers/rtc/rtc-isl1208.c
> +++ b/drivers/rtc/rtc-isl1208.c
> @@ -370,19 +370,16 @@ isl1208_i2c_set_alarm(struct i2c_client *client, struct rtc_wkalrm *alarm)
> struct rtc_time *alarm_tm = &alarm->time;
> u8 regs[ISL1208_ALARM_SECTION_LEN] = { 0, };
> const int offs = ISL1208_REG_SCA;
> - unsigned long rtc_secs, alarm_secs;
> + time64_t rtc_secs, alarm_secs;
> struct rtc_time rtc_tm;
> int err, enable;
>
> err = isl1208_i2c_read_time(client, &rtc_tm);
> if (err)
> return err;
> - err = rtc_tm_to_time(&rtc_tm, &rtc_secs);
> - if (err)
> - return err;
> - err = rtc_tm_to_time(alarm_tm, &alarm_secs);
> - if (err)
> - return err;
> +
> + rtc_secs = rtc_tm_to_time64(&rtc_tm);
> + alarm_secs = rtc_tm_to_time64(alarm_tm);
>
> /* If the alarm time is before the current time disable the alarm */
> if (!alarm->enabled || alarm_secs <= rtc_secs)
>
next prev parent reply other threads:[~2015-06-01 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 15:04 [PATCH RESEND 1/3] drivers/rtc/pcf8563: Replace deprecated rtc_time_to_tm() and rtc_tm_to_time() Xunlei Pang
2015-05-29 15:04 ` [PATCH RESEND 2/3] drivers/rtc/isl1208: Replace deprecated rtc_tm_to_time() Xunlei Pang
2015-06-01 19:49 ` Arnd Bergmann [this message]
2015-05-29 15:04 ` [PATCH RESEND 3/3] drivers/rtc/sunxi: " Xunlei Pang
2015-06-01 19:53 ` Arnd Bergmann
2015-06-02 3:21 ` pang.xunlei
2015-06-01 19:46 ` [PATCH RESEND 1/3] drivers/rtc/pcf8563: Replace deprecated rtc_time_to_tm() and rtc_tm_to_time() Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2324798.u1fgEdZHfl@wuerfel \
--to=arnd@arndb.de \
--cc=a.zummo@towertech.it \
--cc=hvr@gnu.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pang.xunlei@linaro.org \
--cc=rtc-linux@googlegroups.com \
--cc=xlpang@126.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).