Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3720175pxu; Mon, 30 Nov 2020 08:58:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJzdUuQIyofY1Ue/EclIQMnbIuF7Rfa/tmoWgKhsleylTc4I8hmeNKBt5f3O2ZKIlToWSCH6 X-Received: by 2002:a17:906:e28c:: with SMTP id gg12mr1369238ejb.74.1606755491644; Mon, 30 Nov 2020 08:58:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606755491; cv=none; d=google.com; s=arc-20160816; b=xVJm1sVGqRfseL4Zw4YoeHUl0Z+BwqfP/GkTz0WS974AlkYyJZVnlD98eSe5aNeRkB iKseQhrHd11ejKVp6UUNW3yafhoTdB65uxZ7yrWJPOuvLhqgl5CO+n+bi6tXXqq03xus gqHhm7MjbyEVHwCzLuXbcKBo2IBCVBgs23J3p+1b0SeeT9ArC+Npm1PnBTXGTAOKrX+O /hxMN0ob5M1vSf4fEk6+WrKtCtHDnhD13yjXGVjJ8CPleIdGLDB6VOclb4dh+DjldN// gI+mdsXHhjOiLLqBZo5Z0M38ld6sQ/wGjjL1aovLVA+wInU2YSVr8xoVXCPuOedDvY37 KGHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=kT41HNW6/8QjI77oQpxWZeUc4Z3aV4n7JVhlOnKOPj4=; b=LXMER/O8TXXuAA3oc4gcupb12jJRaZpHmXUGrChgXzn1iV6IOkLlzin/wQGW/06ZER S0ZpZ9+n9EIHIwQoj/3wcqnsrLLjwNRy9Ia9yYyWjkhm12La7qU+Nwnyz0gsgjxmmwkj bv3y32K2ZM7JaQx7VSSmwi4WPVIuR0eFnJegdso2Vg3YSGagrrwlCkJhJfk2UfeAQvhh 8aAxYoXOZraRmcr6pojdYgZ27vjMeEoxxM41FN9lBoAm+a5Q6RTAO40J/gYVvaAmf3wf Mrc81PTWH3NPRGQHTri6VKuESt3LKJNUIE3REVVLOx82tdcqT09pE7z3yD48VYObnrlj lsHg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gb31si10616098ejc.465.2020.11.30.08.57.33; Mon, 30 Nov 2020 08:58:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726970AbgK3Q4N (ORCPT + 99 others); Mon, 30 Nov 2020 11:56:13 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:45579 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728148AbgK3Q4N (ORCPT ); Mon, 30 Nov 2020 11:56:13 -0500 Received: from callcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AUGrdfr005363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Nov 2020 11:53:40 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 6172A420136; Mon, 30 Nov 2020 11:53:39 -0500 (EST) Date: Mon, 30 Nov 2020 11:53:39 -0500 From: "Theodore Y. Ts'o" To: "Jason A. Donenfeld" Cc: duwe@lst.de, Linus Torvalds , Stephan =?iso-8859-1?Q?M=FCller?= , Willy Tarreau , Linux Crypto Mailing List , Nicolai Stange , LKML , Arnd Bergmann , "Eric W. Biederman" , "Alexander E. Patrakov" , "Ahmed S. Darwish" , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , zhangjs , Andy Lutomirski , Florian Weimer , Lennart Poettering , Peter Matthias , Marcelo Henrique Cerri , Neil Horman , Randy Dunlap , Julia Lawall , Dan Carpenter , And y Lavr , Eric Biggers , Ard Biesheuvel , Petr Tesarik , simo@redhat.com Subject: Re: drivers/char/random.c needs a (new) maintainer Message-ID: <20201130165339.GE5364@mit.edu> References: <20201130151231.GA24862@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Mon, Nov 30, 2020 at 04:15:23PM +0100, Jason A. Donenfeld wrote: > I am willing to maintain random.c and have intentions to have a > formally verified RNG. I've mentioned this to Ted before. > > But I think Ted's reluctance to not accept the recent patches sent to > this list is mostly justified, and I have no desire to see us rush > into replacing random.c with something suboptimal or FIPSy. Being a maintainer is not about *accepting* patches, it's about *reviewing* them. I do plan to make time to catch up on reviewing patches this cycle. One thing that would help me is if folks (especially Jason, if you would) could start with a detailed review of Nicolai's patches. His incremental approach is I believe the best one from a review perspective, and certainly his cleanup patches are ones which I would expect are no-brainers. - Ted