All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sasha Levin <sashal@kernel.org>
Cc: "Rantala,
	Tommi T. (Nokia - FI/Espoo)" <tommi.t.rantala@nokia.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tytso@mit.edu" <tytso@mit.edu>
Subject: Re: 4.14 "random: add a config option to trust the CPU's hwrng"
Date: Thu, 7 Feb 2019 12:28:09 +0100	[thread overview]
Message-ID: <20190207112809.GC3120@kroah.com> (raw)
In-Reply-To: <20190206192613.GB4119@sasha-vm>

On Wed, Feb 06, 2019 at 02:26:13PM -0500, Sasha Levin wrote:
> On Wed, Feb 06, 2019 at 11:44:36AM +0000, Rantala, Tommi T. (Nokia - FI/Espoo) wrote:
> > Hi stable maintainers,
> > 
> > Can you consider including these "random" patches in 4.14.y?
> > 
> > These are very useful in fixing esp. first-bootup delays of VMs due to
> > entropy starvation.
> > 
> > 
> > commit 39a8883a2b989d1d21bd8dd99f5557f0c5e89694
> > Author: Theodore Ts'o <tytso@mit.edu>
> > Date:   Tue Jul 17 18:24:27 2018 -0400
> > 
> >    random: add a config option to trust the CPU's hwrng
> > 
> > commit 9b25436662d5fb4c66eb527ead53cab15f596ee0
> > Author: Kees Cook <keescook@chromium.org>
> > Date:   Mon Aug 27 14:51:54 2018 -0700
> > 
> >    random: make CPU trust a boot parameter
> 
> This really looks like a new feature to me. The "old" behaviour of not
> trusting RDRAND-like randomness was by-design rather than an oversight.

I agree with Sasha, this looks like a new feature.  If you really want
this new functionality, just use 4.19 or newer, right?

thanks,

greg k-h

  reply	other threads:[~2019-02-07 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 11:44 4.14 "random: add a config option to trust the CPU's hwrng" Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-06 19:26 ` Sasha Levin
2019-02-07 11:28   ` Greg KH [this message]
2019-02-07 16:25     ` Theodore Y. Ts'o

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=20190207112809.GC3120@kroah.com \
    --to=greg@kroah.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tommi.t.rantala@nokia.com \
    --cc=tytso@mit.edu \
    /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.