From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751357AbdFFHqA (ORCPT ); Tue, 6 Jun 2017 03:46:00 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:49218 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750959AbdFFHp6 (ORCPT ); Tue, 6 Jun 2017 03:45:58 -0400 Date: Tue, 6 Jun 2017 09:45:52 +0200 From: Greg Kroah-Hartman To: "Jason A. Donenfeld" Cc: "Theodore Ts'o" , Linux Crypto Mailing List , LKML , kernel-hardening@lists.openwall.com Subject: Re: [PATCH RFC v2 0/8] get_random_bytes_wait family of APIs Message-ID: <20170606074552.GA10432@kroah.com> References: <20170605034757.4803-1-Jason@zx2c4.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 06, 2017 at 01:47:25AM +0200, Jason A. Donenfeld wrote: > As this RFC series matures, all the changes are in this branch here, to look at: > > https://git.zx2c4.com/linux-dev/log/?h=jd/rng-blocker > > Ted -- there's one, in particular, that should probably be picked up > regardless of the rest, and that's "random: invalidate batched entropy > after crng init". Hopefully though, we can develop that in relation > with the rest and make this a proper series. If it's needed no matter what, can you make it the first patch in the series? And does it need to go to any older kernels as well? thanks, greg k-h