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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 03187C43215 for ; Tue, 19 Nov 2019 10:06:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CED3320857 for ; Tue, 19 Nov 2019 10:06:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574157977; bh=rWQ/lkGgBOVp8kUnHcoEXqH8/pa6VQ2R1kl+dVXu2DM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=kEMN11uk0EjnrueqgQsKCmxV6QY8B0ZwladY3GmvwOUjhQKBQYXW02H7RlnyP8kNe cxmXuJ0B7Rb/Ks86/sNFGJfU8ikNJOILgeZUj3twRrJz8PY8J8QPkeIktYZDBdjbZC ZbATO6ej1NDw/uSHiGs0o87z/jEzNCwCAo4ZOw7U= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727586AbfKSKGQ (ORCPT ); Tue, 19 Nov 2019 05:06:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:40724 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726265AbfKSKGQ (ORCPT ); Tue, 19 Nov 2019 05:06:16 -0500 Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4DCCF2231A for ; Tue, 19 Nov 2019 10:06:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574157975; bh=rWQ/lkGgBOVp8kUnHcoEXqH8/pa6VQ2R1kl+dVXu2DM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=HgEuceO+k7duJ5ZWetb2pSprvk67YQ3lLR55QT/dKRSFqKd5jdsyp90096gaCiqWK U1/1NRmX/v72AYEA+0d4UzKE26dgernmvyW11konXl1yiL3puHqL84IEJIvA9bo5bI 7BEM7bQ4uTCCXs3dq2Af1HwkV+5UpLVkWulNNty8= Received: by mail-wr1-f54.google.com with SMTP id a15so23049948wrf.9 for ; Tue, 19 Nov 2019 02:06:15 -0800 (PST) X-Gm-Message-State: APjAAAVgnmzPuUswXoKmjCcAOfr0QW1ZdWjm9EoosllZXPnfAT9xpMz6 MPPlDlbKXBDntsAr1CJeDMqg2fRKRaycrc3CpWngSg== X-Google-Smtp-Source: APXvYqwXqnJ2b6go4d2so794PYr2fq3ATh1U8fgULvNYyIHkM7sbcTs+xnBfZqXou6vX7C0E4cF57QGLaw14xCVaaZw= X-Received: by 2002:a5d:640b:: with SMTP id z11mr34817132wru.195.1574157973828; Tue, 19 Nov 2019 02:06:13 -0800 (PST) MIME-Version: 1.0 References: <2476454.l8LQlgn7Hv@positron.chronox.de> <4EB89769-7A2C-4A03-A832-9A0539DD3336@amacapital.net> <3043322.Kq9igzfA0K@positron.chronox.de> In-Reply-To: <3043322.Kq9igzfA0K@positron.chronox.de> From: Andy Lutomirski Date: Tue, 19 Nov 2019 02:06:02 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v25 03/12] LRNG - /proc interface To: =?UTF-8?Q?Stephan_M=C3=BCller?= Cc: Arnd Bergmann , Greg Kroah-Hartman , Linux Crypto Mailing List , LKML , Linux API , "Eric W. Biederman" , "Alexander E. Patrakov" , "Ahmed S. Darwish" , "Theodore Y. Ts'o" , Willy Tarreau , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , zhangjs , Andy Lutomirski , Florian Weimer , Lennart Poettering , Nicolai Stange , "Peter, Matthias" , Marcelo Henrique Cerri , Roman Drahtmueller , Neil Horman Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 17, 2019 at 4:16 AM Stephan M=C3=BCller w= rote: > > Am Samstag, 16. November 2019, 17:39:40 CET schrieb Andy Lutomirski: > > Hi Andy, > > > > On Nov 16, 2019, at 1:40 AM, Stephan M=C3=BCller wrote: > > > > > > =EF=BB=BFThe LRNG /proc interface provides the same files as the lega= cy > > > /dev/random. These files behave identically. Yet, all files are > > > documented at [1]. > > > > Why? > > I am not sure here: are you referring to the documentation? Or the one > additional file? > > If it is the documentation, do you want me to add it to the patch descrip= tion? > I initially did not add it as these files were present and seemingly know= n > what they provide. But I would add that documentation to the patch descri= ption > if this is desired. Sorry, I should have been a lot more explicit. Why do you want to add a new interface to read the RNG? What's wrong with the old one? I think your patch description should explain the purpose of the patch.