The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Benjamin ROBIN <dev@benjarobin.fr>, jstultz@google.com
Cc: sboyd@kernel.org, linux-kernel@vger.kernel.org,
	Benjamin ROBIN <dev@benjarobin.fr>
Subject: Re: [PATCH] ntp: Make sure RTC is synchronized for any time jump
Date: Wed, 16 Oct 2024 00:28:31 +0200	[thread overview]
Message-ID: <87y12pc86o.ffs@tglx> (raw)
In-Reply-To: <20241006165805.47330-1-dev@benjarobin.fr>

On Sun, Oct 06 2024 at 18:58, Benjamin ROBIN wrote:
> @@ -2553,7 +2556,6 @@ int do_adjtimex(struct __kernel_timex *txc)
>  {
>  	struct timekeeper *tk = &tk_core.timekeeper;
>  	struct audit_ntp_data ad;
> -	bool offset_set = false;
>  	bool clock_set = false;
>  	struct timespec64 ts;
>  	unsigned long flags;
> @@ -2576,7 +2578,6 @@ int do_adjtimex(struct __kernel_timex *txc)
>  		if (ret)
>  			return ret;
>  
> -		offset_set = delta.tv_sec != 0;
>  		audit_tk_injoffset(delta);
>  	}
>  
> @@ -2610,7 +2611,7 @@ int do_adjtimex(struct __kernel_timex *txc)
>  	if (clock_set)
>  		clock_was_set(CLOCK_SET_WALL);
>  
> -	ntp_notify_cmos_timer(offset_set);
> +	ntp_notify_cmos_timer(false);

Can you please add a comment why this does not need to cancel the
hrtimer? It took me a few looks to validate that this is correct. Six
months down the road we both forgot about it. :)

Also can you please rebase this on top of

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core

which has a larger change of the NTP code.

Thanks,

        tglx



  reply	other threads:[~2024-10-15 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 16:58 [PATCH] ntp: Make sure RTC is synchronized for any time jump Benjamin ROBIN
2024-10-15 22:28 ` Thomas Gleixner [this message]
2024-10-27 17:42   ` Benjamin ROBIN

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=87y12pc86o.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=dev@benjarobin.fr \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    /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