From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] timekeeping: contribute wall clock to rng on time change
Date: Thu, 23 Jun 2022 10:39:09 -0700 [thread overview]
Message-ID: <YrSlPUhqhOosqpMH@sol.localdomain> (raw)
In-Reply-To: <20220623165226.1335679-1-Jason@zx2c4.com>
On Thu, Jun 23, 2022 at 06:52:26PM +0200, Jason A. Donenfeld wrote:
> The rng's random_init() function contributes the real time to the rng at
> boot time, so that events can at least start in relation to something
> particular in the real world. But this clock might not yet be set that
> point in boot, so nothing is contributed. In addition, the relation
> between minor clock changes from, say, NTP, and the cycle counter is
> potentially useful entropic data.
>
> This commit addresses this by mixing in a time stamp on calls to
> settimeofday and adjtimex. No entropy is credited in doing so, so it
> doesn't make initialization faster, but it is still useful input to
> have.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Good idea.
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 8e4b3c32fcf9..ad55da792f13 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
This doesn't compile:
kernel/time/timekeeping.c: In function ‘do_settimeofday64’:
kernel/time/timekeeping.c:1350:9: error: implicit declaration of function ‘add_device_randomness’ [-Werror=implicit-function-declaratio ]
1350 | add_device_randomness(&xt, sizeof(xt));
| ^~~~~~~~~~~~~~~~~~~~~
> @@ -1346,6 +1346,9 @@ int do_settimeofday64(const struct timespec64 *ts)
> if (!ret)
> audit_tk_injoffset(ts_delta);
>
> + ktime_get_real_ts64(&xt);
> + add_device_randomness(&xt, sizeof(xt));
> +
> return ret;
Isn't the new time already available in 'ts'? Is the call to
ktime_get_real_ts64() necessary?
> }
> EXPORT_SYMBOL(do_settimeofday64);
> @@ -2475,6 +2478,9 @@ int do_adjtimex(struct __kernel_timex *txc)
>
> ntp_notify_cmos_timer();
>
> + ktime_get_real_ts64(&ts);
> + add_device_randomness(&ts, sizeof(ts));
> +
> return ret;
> }
adjtimex() actually triggers a gradual adjustment of the clock, rather than
setting it immediately. Is there a way to mix in the target time rather than
the current time as this does?
- Eric
next prev parent reply other threads:[~2022-06-23 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 16:52 [PATCH] timekeeping: contribute wall clock to rng on time change Jason A. Donenfeld
2022-06-23 17:39 ` Eric Biggers [this message]
2022-06-23 18:04 ` Jason A. Donenfeld
2022-06-23 18:05 ` [PATCH v2] " Jason A. Donenfeld
2022-06-23 18:53 ` Eric Biggers
2022-06-23 18:56 ` Jason A. Donenfeld
2022-06-23 19:00 ` [PATCH v3] " Jason A. Donenfeld
2022-06-23 19:10 ` Eric Biggers
2022-06-23 19:11 ` Jason A. Donenfeld
2022-06-23 19:12 ` [PATCH v4] " Jason A. Donenfeld
2022-06-23 19:36 ` Eric Biggers
2022-06-30 13:06 ` Jason A. Donenfeld
2022-06-23 18:04 ` [PATCH] " kernel test robot
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=YrSlPUhqhOosqpMH@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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 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).