From: Andrew Morton <akpm@linux-foundation.org>
To: Hyogi Gim <hyogi.gim@lge.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] driver/rtc/class.c: check the error after rtc_read_time()
Date: Wed, 23 Jul 2014 14:56:34 -0700 [thread overview]
Message-ID: <20140723145634.656752d0fe2fa124db48b4fc@linux-foundation.org> (raw)
In-Reply-To: <1405412723-10062-1-git-send-email-hyogi.gim@lge.com>
On Tue, 15 Jul 2014 17:25:23 +0900 Hyogi Gim <hyogi.gim@lge.com> wrote:
> In rtc_suspend() and rtc_resume(), the error after rtc_read_time() is not
> checked. If rtc device fail to read time, we cannot guarantee the following
> process.
>
> Add the verification code for returned rtc_read_time() error.
>
> ...
>
> --- a/drivers/rtc/class.c
> +++ b/drivers/rtc/class.c
> @@ -53,6 +53,7 @@ static int rtc_suspend(struct device *dev)
> struct rtc_device *rtc = to_rtc_device(dev);
> struct rtc_time tm;
> struct timespec delta, delta_delta;
> + int err;
>
> if (has_persistent_clock())
> return 0;
> @@ -61,7 +62,12 @@ static int rtc_suspend(struct device *dev)
> return 0;
>
> /* snapshot the current RTC and system time at suspend*/
> - rtc_read_time(rtc, &tm);
> + err = rtc_read_time(rtc, &tm);
> + if (err < 0) {
> + pr_debug("%s: fail to read rtc time\n", dev_name(&rtc->dev));
> + return 0;
> + }
OK, it makes no sense to go ahead and set the system time from a
garbage rtc_time.
But I'm wondering if we should propagate the error back to the
rtc_suspend() caller. What does the PM core do if a particular
device's ->suspend or ->resume fails?
> getnstimeofday(&old_system);
> rtc_tm_to_time(&tm, &old_rtc.tv_sec);
>
> @@ -94,6 +100,7 @@ static int rtc_resume(struct device *dev)
> struct rtc_time tm;
> struct timespec new_system, new_rtc;
> struct timespec sleep_time;
> + int err;
>
> if (has_persistent_clock())
> return 0;
> @@ -104,7 +111,12 @@ static int rtc_resume(struct device *dev)
>
> /* snapshot the current rtc and system time at resume */
> getnstimeofday(&new_system);
> - rtc_read_time(rtc, &tm);
> + err = rtc_read_time(rtc, &tm);
> + if (err < 0) {
> + pr_debug("%s: fail to read rtc time\n", dev_name(&rtc->dev));
> + return 0;
> + }
> +
> if (rtc_valid_tm(&tm) != 0) {
> pr_debug("%s: bogus resume time\n", dev_name(&rtc->dev));
> return 0;
next prev parent reply other threads:[~2014-07-23 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 8:25 [PATCH] driver/rtc/class.c: check the error after rtc_read_time() Hyogi Gim
2014-07-23 21:56 ` Andrew Morton [this message]
2014-07-23 23:47 ` Rafael J. Wysocki
2014-07-23 23:49 ` Rafael J. Wysocki
2014-07-24 0:19 ` Andrew Morton
2014-08-07 1:58 ` Hyogi Gim
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=20140723145634.656752d0fe2fa124db48b4fc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=hyogi.gim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rtc-linux@googlegroups.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