From: Stephan =?ISO-8859-1?Q?M=FCller?= Subject: Re: [kernel-hardening] Re: [PATCH v4 06/13] iscsi: ensure RNG is seeded before use Date: Sun, 18 Jun 2017 10:04:58 +0200 Message-ID: <2639082.PtrrGWOPPL@positron.chronox.de> References: <20170606174804.31124-1-Jason@zx2c4.com> <02d60ed4-4207-dd7d-8826-0f9f7f4e966d@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "Jason A. Donenfeld" , Theodore Ts'o , Linux Crypto Mailing List , LKML , kernel-hardening@lists.openwall.com, Greg Kroah-Hartman , David Miller , Eric Biggers , "Nicholas A. Bellinger" , Chris Leech , open-iscsi@googlegroups.com To: Lee Duncan Return-path: In-Reply-To: <02d60ed4-4207-dd7d-8826-0f9f7f4e966d@suse.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org Am Samstag, 17. Juni 2017, 05:45:57 CEST schrieb Lee Duncan: Hi Lee, > In your testing, how long might a process have to wait? Are we talking > seconds? Longer? What about timeouts? > In current kernels (starting with 4.8) this timeout should clear within a few seconds after boot. In older kernels (pre 4.8), my KVM takes up to 90 seconds to reach that seeding point. I have heard that on IBM System Z this trigger point requires minutes to be reached. Ciao Stephan