Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp815466ybc; Tue, 19 Nov 2019 09:41:31 -0800 (PST) X-Google-Smtp-Source: APXvYqw14edr6pP7VdEJ6ljkE8EMzsi3IcY6tI58tjRWYQVcGPlKFk+NEHEfIVSxmvXmpd4FbSkL X-Received: by 2002:adf:d091:: with SMTP id y17mr40435529wrh.182.1574185290944; Tue, 19 Nov 2019 09:41:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574185290; cv=none; d=google.com; s=arc-20160816; b=YDsFzV9MuPwWHPlbVtHgBBPRr7mXkguT3uiYbxU2Y/VVqTVC6sNKlv1qzTMNsaUgf8 KJDxsB8VAeOeJlBVq2r2fUEaccCf+yos9TYxZtrcmcHO7j2zgmqbwgvvnaQQL8vpOR/8 sTlKramuFxnmyLxrH5WWJpNVilSOj5Sn2hixoLC6EdASTZGLjEuu7T2vnX4PlRzY/Tdw cN3Fo/dvj/nU3giRBTbWc94QKkXOg2wL3Hkw1oEvmpOVbvnzJef3cajHhj4logU4cNEn +FSS0KueutyH2q9O3BFK2DT6AivCoWx6hkZ1jpuNU8+g0ALw4O0k+cK/HaTYgAIwikRO tpzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=+ZVpHo5fo9dXLfnJP4xuB3MCQBjB3RnOmAPXQL2Ltoc=; b=fz31MGwXMyLM32/eUukCU1dzPF44dIkMfXo5dMI7BUXohbDUbKN/3HL+xoT9g73sDT H+PSTzxgD1q6B6neiQkQzWWRktBB4u6TzCTCFiMclVWDYeWpwyTHdNozhGoqsX6DiriE //+IS71CzHBe0LBOaqGsLvBiWgMRp+zN3OZujdbw8KLJIA96FuDZvXllovRTkGa0pb3x Rs50hWxB/E1aVYMimiWgOX44H4v2jxyXOzsRSAERoM6wPKZf34YgO+1kAV1qtdjA9i/L x2nwlCL2848VPb8T4R1Au26zTZKMMI+2uqDIYI4ev+FAwsPYFV62qbS9Zy9BRtiXM0tp uoTA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QNdH6mi5; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g54si10550724eda.101.2019.11.19.09.41.05; Tue, 19 Nov 2019 09:41:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QNdH6mi5; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728442AbfKSRk5 (ORCPT + 99 others); Tue, 19 Nov 2019 12:40:57 -0500 Received: from mail.kernel.org ([198.145.29.99]:44382 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728431AbfKSRk5 (ORCPT ); Tue, 19 Nov 2019 12:40:57 -0500 Received: from mail-wm1-f50.google.com (mail-wm1-f50.google.com [209.85.128.50]) (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 A054622360 for ; Tue, 19 Nov 2019 17:40:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574185256; bh=CluRblEFMUETyKbYj2Mbw+FlclYGBj6WdguG//F2G7Q=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=QNdH6mi5PiBtuEUA+43zu2S/TU+LbiB0e005F3zS94ECiaj4JE+mdeafj73BfHmPV EdXo8E+E08nSEn2/f6U2g/kBww828l/aRDCGIhlCgTGANqLIlsgR91hNi5+zRNetYB qZqmwLE61dEejb4RB62BEBD6Va8/0rIAsEmn4vb4= Received: by mail-wm1-f50.google.com with SMTP id z19so4747155wmk.3 for ; Tue, 19 Nov 2019 09:40:56 -0800 (PST) X-Gm-Message-State: APjAAAXXdDXFkBy6o1Fym5p4a3bqyHAq8lAk0dCm3MOv207FueEEAohC 0dlJne3nO4UKHWQrw8wHoqpKqR/NtAB3zzs4zuLmSA== X-Received: by 2002:a1c:f210:: with SMTP id s16mr5247240wmc.76.1574185255074; Tue, 19 Nov 2019 09:40:55 -0800 (PST) MIME-Version: 1.0 References: <2476454.l8LQlgn7Hv@positron.chronox.de> <3043322.Kq9igzfA0K@positron.chronox.de> <5323691.yyFvDVlHDV@tauon.chronox.de> In-Reply-To: <5323691.yyFvDVlHDV@tauon.chronox.de> From: Andy Lutomirski Date: Tue, 19 Nov 2019 09:40:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v25 03/12] LRNG - /proc interface To: Stephan Mueller Cc: Andy Lutomirski , 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 , 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-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Nov 19, 2019 at 2:57 AM Stephan Mueller wrote= : > > Am Dienstag, 19. November 2019, 11:06:02 CET schrieb Andy Lutomirski: > > Hi Andy, > > > On Sun, Nov 17, 2019 at 4:16 AM Stephan M=C3=BCller wrote: > > > 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 = legacy > > > > > /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 on= e > > > additional file? > > > > > > If it is the documentation, do you want me to add it to the patch > > > description? I initially did not add it as these files were present a= nd > > > seemingly known what they provide. But I would add that documentation= to > > > the patch description 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? > > There is nothing wrong at all. I actually want to be 100% API and ABI > compliant with the existing random.c. Thus, the list of the sysctls are > identical to the existing random.c with the same behavior (hence I skippe= d the > documentation of these files). Whoops, I misunderstood your commit message. You said "The LRNG /proc interface provides the same files as the legacy /dev/random.". I assumed that meant that you had a file in /proc that worked like /dev/random. So never mind.