Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751649AbdFFMV6 (ORCPT ); Tue, 6 Jun 2017 08:21:58 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:59377 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751345AbdFFMV4 (ORCPT ); Tue, 6 Jun 2017 08:21:56 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170606005108.5646-1-Jason@zx2c4.com> <20170606005108.5646-3-Jason@zx2c4.com> From: "Jason A. Donenfeld" Date: Tue, 6 Jun 2017 14:21:53 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 02/13] random: add get_random_{bytes,u32,u64,int,long,once}_wait family To: noloader@gmail.com Cc: "Theodore Ts'o" , Linux Crypto Mailing List , LKML , kernel-hardening@lists.openwall.com, Greg Kroah-Hartman , David Miller 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: 436 Lines: 10 On Tue, Jun 6, 2017 at 7:11 AM, Jeffrey Walton wrote: > On Mon, Jun 5, 2017 at 8:50 PM, Jason A. Donenfeld wrote: >> These functions are simple convenience wrappers that call >> wait_for_random_bytes before calling the respective get_random_* >> function. > > It may be advantageous to add a timeout, too. This was in v1, but was removed because of a lack of particular use case in this context.