Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jacob Lifshay <>
Subject: why not use ktime_get_clocktai_ts64
Date: Wed, 15 Jun 2022 18:48:08 -0700	[thread overview]
Message-ID: <> (raw)

I was reading in noise.c and noticed you use ktime_get_real_ts64 and
do manual adjustments (the current code is broken if/when there's
another leap second) rather than using ktime_get_clocktai_ts64 which
already handles compensation for leap seconds.

Is there a reason for that?


             reply	other threads:[~2022-06-17 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  1:48 Jacob Lifshay [this message]
2022-06-17 11:56 ` Jason A. Donenfeld
2022-06-19  6:16   ` Jacob Lifshay

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: why not use ktime_get_clocktai_ts64' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).