From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 818EDC33CB3 for ; Tue, 28 Jan 2020 07:52:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4C4052467E for ; Tue, 28 Jan 2020 07:52:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580197946; bh=BWZI1SGP7I1eCA0zPpPT/HaXMZfAirxOfLE9j6CTh44=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=kDNvMdtxzjFKZggzyTi6ZlxHeTfmvYqLcV0POykilx/ucEcu380zyb07afserMwIz m40jgR1CUzIKHfJkpLZDZkxof7H7KPhMJPVxeBe9pIp2InOlP0XPl85aZ1E68WwPCQ KurVri1XsKz1ydy2MPfrpOqGfuf6XsBJbM3+TAsg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725867AbgA1Hw0 (ORCPT ); Tue, 28 Jan 2020 02:52:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:55438 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725810AbgA1HwZ (ORCPT ); Tue, 28 Jan 2020 02:52:25 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F22332465B; Tue, 28 Jan 2020 07:52:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580197945; bh=BWZI1SGP7I1eCA0zPpPT/HaXMZfAirxOfLE9j6CTh44=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=DYRBxo04WvER8RAJItw6Ee7fLszcPEyzIHXO9zqfTT/ukSPDMDdbR9urYLclfRCWA mahd78FNLqfHeDsfo5/ShFFuqmfSvZtZOcYYbvXkgBjUJy6F4ZytBAV6PRN+kRUWTy VYbFyKd7I63kpTj+xxubCPXq8HjaEUrhsPZzYkpw= Date: Tue, 28 Jan 2020 08:52:23 +0100 From: Greg KH To: Noah Meyerhans Cc: stable@vger.kernel.org Subject: Re: Please apply 50ee7529ec45 ("random: try to actively add entropy rather than passively wait for it") to 4.19.y Message-ID: <20200128075223.GD2105706@kroah.com> References: <20200127230214.GC25530@morgul.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200127230214.GC25530@morgul.net> Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Jan 27, 2020 at 06:02:14PM -0500, Noah Meyerhans wrote: > As detailed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948519 and > https://wiki.debian.org/BoottimeEntropyStarvation, lack of boot-time entropy > can contribute to multi-minute pauses during system initialization in some > hardware configurations. While userspace workarounds, e.g. haveged, are > documented, the in-kernel jitter entropy collector eliminates the need for such > workarounds. > > It cherry-picks cleanly to 4.19.y and 4.14.y. I'm particularly interested > in the former. > > Thanks for considering this. Please cc: the developers of that commit, and the maintainer of that code, and we will be glad to consider it if they agree it is viable for those kernels. Personally, this looks like a "new feature" to me, if you really need this, what is preventing you from moving to a newer kernel version? thanks, greg k-h