Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp231290imj; Thu, 7 Feb 2019 03:29:34 -0800 (PST) X-Google-Smtp-Source: AHgI3IbezxE1u087lNnPSLeGmcgvFbgcOJyBwoR3va65uh7iivovIl7tT2BsLiewh2G80xlmmjAG X-Received: by 2002:a62:5c1:: with SMTP id 184mr15544322pff.165.1549538974759; Thu, 07 Feb 2019 03:29:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549538974; cv=none; d=google.com; s=arc-20160816; b=OfTo2AWQxn7YekMeWYisb0s7DgTOY03g5bDH1Ly16yW+X/5ixnvB5WGElCAGiQpXbg gGXreP8jPOTyyd90fb+87fan9mtQ0YpYNnd07hKvAnXPe4qsBL3iz9GXXB5sVs7vcOZF Bc1iG8ACX36V9x/5V/G9GTfdEJ9N7/sWt8qXzyxZEtNK9ErjKETdnliGCDT3vV2ruIQl mXUEmOVlbmhAHrIGcZsQfrrKBPsmLulzJVVtmkCYbAKobm6iY5S4V03qpbL5xnonFPne fQLscAFx5DVL20LmaGONOheFsJkwYohVHL2BJBs99I24IIBAyJJs+gBmknqa+5x+YmVR Ha9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=8d70nJINauXKQ64kXl64/bRBuTmk/TI6qspVL3A5JjI=; b=ENU1cwHyyW2MQ2RP78GjM1c9S/BIsb4PHmL86hJ0e0owhEUoQcQ0WB9UoL/EeYV2d3 pBSpa2o5dYLM2Ni/iumkjjiGtr6i2CZHNS9rx0NwwYaNFkZhB2WUZijvxSKSs1t6DjSJ 1t7MMwT6ww3vkYLo/kkPimxUU+8lAiKrne3RbstIkB5CHPDNJ9bA8cpKTaJ3EAosHfoY 6yRJ6A8dcQdy/o8Jg4te9Kay90WoK5DJyrlIFepPr/3QBem7r0DpkUzYUwly0wefhHkb l3a5eMfAKvsFYN9OFSC2Gd5079jjPk0Ew7ZbRsvh6CymTsJrTrcb4vjNwE8k+sArGjoo /4xQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b="A1P3i/9b"; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=Gi92Kxqj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x74si9189304pfe.23.2019.02.07.03.29.19; Thu, 07 Feb 2019 03:29:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b="A1P3i/9b"; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=Gi92Kxqj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727166AbfBGL2N (ORCPT + 99 others); Thu, 7 Feb 2019 06:28:13 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:51145 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726691AbfBGL2N (ORCPT ); Thu, 7 Feb 2019 06:28:13 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C808621C1B; Thu, 7 Feb 2019 06:28:11 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Thu, 07 Feb 2019 06:28:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=8d70nJINauXKQ64kXl64/bRBuTm k/TI6qspVL3A5JjI=; b=A1P3i/9btDSbAl6EcB8GSUcaezdMV5l1qmZYkkCEDlF bARK10Kp+PQDimKLKIuZ15/ZM8I1fuaqNp9skV5qXKK9jU20TmHtENLhWHt2gn29 fTDozZBPwsGfKy16gbInrPb+pKWQkoMejPBVuz3bQZVdLuqlRk+erBz9QbiLDQvS fJjJJbu18/tthKUktHJ7oixnsBCLFuc6d5jWZW2oRl6ijU7HBXbenkTY9xNHc+bV EcSFwAheNVJAPfrUfExneuz2MNbKsTyKEWiXLBAm0016dJVgjYG/hm+Xgsd3fs0g rm5Al9ZqnIteHelXQ43PGoHXaHn2AVSSb4wORY3U1xg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=8d70nJ INauXKQ64kXl64/bRBuTmk/TI6qspVL3A5JjI=; b=Gi92KxqjlDLfhWvEE+5GE/ 037NAXI0qYycpR0aHq5LGZg7DLoP1OT1Rb9GLAZ0or0e2xx0g8oGwguM7cEAmGuP /8vOetSkzu/Ag4B26uGufaAtbD4wzX6CtxzuIQI5oY6xFKdpsNKCHp6RwF3tv1ph pN/tRkO4UF35bf3L+UjVamqwxdIvEw4GVKXQXZYnPXCZ+I881TX94TCF9l81xgxT CPj/m4K+SJ/Hpr4qgmnxLlpjC/wLvUsawR3wF9gEPnYw1Bn+Hy5Q5fGgsuOGSKHL UXTwUAk1Js0EAMYEtQteoRleBPvqlQxqNgJlkUM5K44jp28rfS4Y5C7zBPRqR64A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrledtgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgg gtuggjfgesthdtredttdervdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhr ohgrhhdrtghomheqnecukfhppeekfedrkeeirdekledruddtjeenucfrrghrrghmpehmrg hilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhmnecuvehluhhsthgvrhfuihiivgep td X-ME-Proxy: Received: from localhost (5356596b.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 888BBE4314; Thu, 7 Feb 2019 06:28:10 -0500 (EST) Date: Thu, 7 Feb 2019 12:28:09 +0100 From: Greg KH To: Sasha Levin Cc: "Rantala, Tommi T. (Nokia - FI/Espoo)" , "stable@vger.kernel.org" , "keescook@chromium.org" , "linux-kernel@vger.kernel.org" , "tytso@mit.edu" Subject: Re: 4.14 "random: add a config option to trust the CPU's hwrng" Message-ID: <20190207112809.GC3120@kroah.com> References: <20190206192613.GB4119@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190206192613.GB4119@sasha-vm> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > 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 > > 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