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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C24F2C433EF for ; Fri, 11 Feb 2022 22:10:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353991AbiBKWKz (ORCPT ); Fri, 11 Feb 2022 17:10:55 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:42608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344005AbiBKWKy (ORCPT ); Fri, 11 Feb 2022 17:10:54 -0500 X-Greylist: delayed 572 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Fri, 11 Feb 2022 14:10:52 PST Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 85EC3D43 for ; Fri, 11 Feb 2022 14:10:52 -0800 (PST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id E34C75800E8; Fri, 11 Feb 2022 17:01:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 11 Feb 2022 17:01:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=5zf6jVEQjwVSQ5ZFe HnTKZGFpRdZHZ64iwTJ9Ju+0KE=; b=LlFvrTcCq1B+2kEzvZkHLSNkaWQr+m3ZZ +0eNXDEcpgjZKJLxRPUU7XKWitNaITB5A24lv7mV5wFNdlg0F/oFQoyenr8w1mH/ tzlG/0nSoAwyu/3ZvJ3nf/TvNmpBOrTo9uwSCv+QOqVFmJo7zB8bXWV8br2jfFt4 8YpVXRleEQuGoWwUV9YZ0z4iJYJjLa2bSPfcjSbC51AF5Su871F1cf9viY3KmNcN QrZMKWh8gPwaTrVWg2hQWLmVHydYnu0E5QTrExMqSyupjRb0QuPAmAMctEZeFKpX S0LNElQDEz4zuHSkj2fotjAV8Fx+pSnHiwVFUtso3CkNry6xR44/w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrieefgdduheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffujgfkfhggtgesthdtredttddtvdenucfhrhhomhephfhinhhnucfv hhgrihhnuceofhhthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgheqnecuggftrfgrth htvghrnhepffduhfegfedvieetudfgleeugeehkeekfeevfffhieevteelvdfhtdevffet uedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepfh hthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 11 Feb 2022 17:01:12 -0500 (EST) Date: Sat, 12 Feb 2022 09:01:19 +1100 (AEDT) From: Finn Thain To: "Jason A. Donenfeld" cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Paul Walmsley , Palmer Dabbelt , Albert Ou , linux-riscv@lists.infradead.org, Geert Uytterhoeven , linux-m68k@lists.linux-m68k.org, Thomas Bogendoerfer , linux-mips@vger.kernel.org, Dominik Brodowski , Eric Biggers , Ard Biesheuvel , Arnd Bergmann , Thomas Gleixner , Andy Lutomirski , Kees Cook , Lennart Poettering , Linus Torvalds , Greg Kroah-Hartman , Theodore Ts'o Subject: Re: [PATCH RFC v0] random: block in /dev/urandom In-Reply-To: <20220211210757.612595-1-Jason@zx2c4.com> Message-ID: References: <20220211210757.612595-1-Jason@zx2c4.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-m68k@vger.kernel.org On Fri, 11 Feb 2022, Jason A. Donenfeld wrote: > + * Reading from /dev/random and /dev/urandom both the same effect as > + * calling getrandom(2) with flags=0. In earlier versions, however, > + * they each had vastly different semantics and should therefore be > + * avoided to prevent backwards compatibility issues. If the end result "should be avoided", then why bother? IOW, how does this improve the ABI? I know you said it's a "panacea" but I'm afraid that's not clear to me and the patch description doesn't explain it.