Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751843AbdFHArm (ORCPT ); Wed, 7 Jun 2017 20:47:42 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:58609 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751433AbdFHArl (ORCPT ); Wed, 7 Jun 2017 20:47:41 -0400 MIME-Version: 1.0 In-Reply-To: <20170608004134.hveeuvojoc2edgjm@thunk.org> References: <20170606174804.31124-1-Jason@zx2c4.com> <20170606174804.31124-6-Jason@zx2c4.com> <20170608004134.hveeuvojoc2edgjm@thunk.org> From: "Jason A. Donenfeld" Date: Thu, 8 Jun 2017 02:47:36 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [kernel-hardening] [PATCH v4 05/13] crypto/rng: ensure that the RNG is ready before using To: "Theodore Ts'o" , "Jason A. Donenfeld" , Linux Crypto Mailing List , LKML , kernel-hardening@lists.openwall.com, Greg Kroah-Hartman , David Miller , Eric Biggers , Herbert Xu Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 595 Lines: 10 On Thu, Jun 8, 2017 at 2:41 AM, Theodore Ts'o wrote: > The use in keys/big_key is _being_ removed, so this commit is > dependent on that commit landing, correct? (Order matters, because > otherwise we don't want to potentially screw up doing a kernel bisect > and causing their kernel to deadlock during the boot while they are > trying to track down an unreleated problem.) Yes. It's actually landing with get_random_bytes, to avoid a dependency problem when merging. After these both lands, I'll submit a third changing that over to get_random_bytes_wait in the right place.