All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Liao <liaoyu15@huawei.com>
To: <john.stultz@linaro.org>
Cc: <tglx@linutronix.de>, <linux-kernel@vger.kernel.org>,
	<liwei391@huawei.com>, <liaoyu15@huawei.com>
Subject: [PATCH v2] timekeeping: Make sure wall_to_monotonic isn't positive
Date: Mon, 13 Dec 2021 21:57:27 +0800	[thread overview]
Message-ID: <20211213135727.1656662-1-liaoyu15@huawei.com> (raw)

After commit e1d7ba873555 ("time: Always make sure wall_to_monotonic
isn't positive"), we can still change wall_to_monotonic to positive
by running the following code:
    int main(void)
    {
        struct timespec time;

        clock_gettime(CLOCK_MONOTONIC, &time);
        time.tv_nsec = 0;
        clock_settime(CLOCK_REALTIME, &time);
        return 0;
    }

The reason is that the parameters of timespec64_compare() may be
unnormalized, and timespec64_compare() simply compare tv_sec,
for example:
  wall_to_monotonic = {tv_sec = -10, tv_nsec = 900000000}
  ts_delta = {tv_sec = -9, tv_nsec = -900000000}

timespec64_compare() result is wall_to_monotonic < ts_delta, but
actually wall_to_monotonic > ts_delta. After normalized, the result
of timespec64_compare() is correct:
  wall_to_monotonic = {tv_sec = -10, tv_nsec = 900000000}
  ts_delta = {tv_sec = -10, tv_nsec = 100000000}

Use timespec64_sub() to ensure ts_delta normalized, and the code
looks more concise.

Signed-off-by: Yu Liao <liaoyu15@huawei.com>
---
 kernel/time/timekeeping.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
index b348749a9fc6..dcdcb85121e4 100644
--- a/kernel/time/timekeeping.c
+++ b/kernel/time/timekeeping.c
@@ -1306,8 +1306,7 @@ int do_settimeofday64(const struct timespec64 *ts)
 	timekeeping_forward_now(tk);
 
 	xt = tk_xtime(tk);
-	ts_delta.tv_sec = ts->tv_sec - xt.tv_sec;
-	ts_delta.tv_nsec = ts->tv_nsec - xt.tv_nsec;
+	ts_delta = timespec64_sub(*ts, xt);
 
 	if (timespec64_compare(&tk->wall_to_monotonic, &ts_delta) > 0) {
 		ret = -EINVAL;
-- 
2.25.1


             reply	other threads:[~2021-12-13 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 13:57 Yu Liao [this message]
2021-12-17 22:16 ` [tip: timers/urgent] timekeeping: Really make sure wall_to_monotonic isn't positive tip-bot2 for Yu Liao

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=20211213135727.1656662-1-liaoyu15@huawei.com \
    --to=liaoyu15@huawei.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwei391@huawei.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.