From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Ts'o Subject: Re: [PATCH v3 2/5] random,x86: Add arch_get_slow_rng_u64 Date: Thu, 17 Jul 2014 06:33:24 -0400 Message-ID: <20140717103324.GJ1491@thunk.org> References: <5778e65d5ca52bebbaa023e177d863e44f098e96.1405546879.git.luto@amacapital.net> <53C6F5A9.80400@zytor.com> <53C703ED.2010605@zytor.com> <53C75733.8060507@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andy Lutomirski , Raghavendra K T , Paolo Bonzini , X86 ML , Bandan Das , Gleb Natapov , kvm list , Srivatsa Vaddagiri , Daniel Borkmann , "linux-kernel@vger.kernel.org" , Kees Cook To: "H. Peter Anvin" Return-path: Content-Disposition: inline In-Reply-To: <53C75733.8060507@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Wed, Jul 16, 2014 at 09:55:15PM -0700, H. Peter Anvin wrote: > On 07/16/2014 05:03 PM, Andy Lutomirski wrote: > >> > > I meant that prandom isn't using rdrand for early seeding. > > > > We should probably fix that. It wouldn't hurt to explicitly use arch_get_random_long() in prandom, but it does use get_random_bytes() in early seed, and for CPU's with RDRAND present, we do use it in init_std_data() in drivers/char/random.c, so prandom is already getting initialized via an RNG (which is effectively a DRBG even if it doesn't pass all of NIST's rules) which is derived from RDRAND. Cheers, - Ted