From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: tglx@linutronix.de
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
stable@vger.kernel.org, ebiggers@kernel.org
Subject: Re: [PATCH v4] timekeeping: contribute wall clock to rng on time change
Date: Thu, 30 Jun 2022 15:06:31 +0200 [thread overview]
Message-ID: <Yr2f13QhFsyxdDS7@zx2c4.com> (raw)
In-Reply-To: <YrTAt2g4gg/2e+5L@sol.localdomain>
Hi Thomas,
On Thu, Jun 23, 2022 at 12:36:23PM -0700, Eric Biggers wrote:
> On Thu, Jun 23, 2022 at 09:12:49PM +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>
> > ---
> > kernel/time/timekeeping.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
>
> Reviewed-by: Eric Biggers <ebiggers@google.com>
Thought I should bump this patch in case you missed it.
Jason
next prev parent reply other threads:[~2022-06-30 13:06 UTC|newest]
Thread overview: 15+ 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
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 [this message]
2022-07-17 21:53 ` [PATCH v4 RESEND] " Jason A. Donenfeld
2022-07-18 12:20 ` Thomas Gleixner
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=Yr2f13QhFsyxdDS7@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ebiggers@kernel.org \
--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 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.