Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp182747pxy; Wed, 21 Apr 2021 22:52:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw9rxIiNxRZPxpUkmHrEW08HvahJfblkUpO6LaZQskRZ1KXFZirRVE3lQ6Ozh0l6dcbf6D/ X-Received: by 2002:a17:902:e8c1:b029:e9:3c98:2dd2 with SMTP id v1-20020a170902e8c1b02900e93c982dd2mr1706048plg.17.1619070742958; Wed, 21 Apr 2021 22:52:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619070742; cv=none; d=google.com; s=arc-20160816; b=hoksjNTHEkIVukMTgll/D31C3BTTQlGJ94rVsLqItfle9ztQv81POrWzIE2gywnoux mxF6wnG/mh5sTjW5zZQjQTroAltU27ydHTnL4KDZ3+S71nPR8ZIwAhyUYHA7SYR6pVr7 2mN5ZcARAhDEerxw86M6vnO12hsLR3nYEwtDOPVjc8NkkaCIV6JJ4qxZocTaF1DJSgAx h52ZpToOOrrFaPaYZYN7BttN1fi+mq2yvBfspLQJW8U9NUY8imqJ52+Q/5jLt4TMdbNE inBOReg5QXDQfSXFv9CsDwAuwjNqVFHorRrvnQ/zMkph76lSXwBkAm6HwAFa2KlpXznE yrWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=kflD9llIZRcLWfayD0oy78y9/DwQMTzKs699qYTnIaE=; b=CkmpGLv6XxJ6zHPCeliQbulz5YpzeRzTg72XlQShthOBUL7EZQj+9RTao9QW09f4nk 59ACCaEaXTwv4XV/vXRNhuj931B580dCRZX/AUrVMQVA3wJwoaj4P1kK8QBcC3Twzcv9 RMVBela+O4+aLQ+fU5wOi+VPuHARIr6UwzTkZAhyI15NTn2U5lz9AbIj8wGjF2+Kkhtc ghLhhTserxF8b6Mr/7ZGgtqurSrbsvgGGDNoIVQCsABjiUkg1baMRttHkL5qefZ/GQQb blF5hc4dyg9Ub99If/3kYfa9gpckONpS2VVCyTv/aX66fJ24+vumvbpyajx++C8p9YMD eJfg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-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 w70si2068965pff.345.2021.04.21.22.52.10; Wed, 21 Apr 2021 22:52:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229962AbhDVFwJ (ORCPT + 99 others); Thu, 22 Apr 2021 01:52:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229533AbhDVFwI (ORCPT ); Thu, 22 Apr 2021 01:52:08 -0400 Received: from zeniv-ca.linux.org.uk (zeniv-ca.linux.org.uk [IPv6:2607:5300:60:148a::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6DD23C06174A for ; Wed, 21 Apr 2021 22:51:34 -0700 (PDT) Received: from viro by zeniv-ca.linux.org.uk with local (Exim 4.94 #2 (Red Hat Linux)) id 1lZSFL-007EQm-Jb; Thu, 22 Apr 2021 05:51:27 +0000 Date: Thu, 22 Apr 2021 05:51:27 +0000 From: Al Viro To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, Linus Torvalds , Aditya Pakki , Kangjie Lu , Qiushi Wu , x86@kernel.org, Bjorn Helgaas , "Rafael J. Wysocki" , Arnd Bergmann , David Airlie , Michael Turquette , Bjorn Andersson , Linus Walleij , Bartosz Golaszewski , Daniel Vetter , Jean Delvare , Guenter Roeck , Jiri Kosina , Will Deacon , Laurent Pinchart , Jakub Kicinski , "David S. Miller" , Johan Hovold , Jiri Slaby , Pablo Neira Ayuso , Johannes Berg , Takashi Iwai Subject: Re: [PATCH 000/190] Revertion of all of the umn.edu commits Message-ID: References: <20210421130105.1226686-1-gregkh@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210421130105.1226686-1-gregkh@linuxfoundation.org> Sender: Al Viro Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 21, 2021 at 02:57:55PM +0200, Greg Kroah-Hartman wrote: > I'll take this through my tree, so no need for any maintainer to worry > about this, but they should be aware that future submissions from anyone > with a umn.edu address should be by default-rejected unless otherwise > determined to actually be a valid fix (i.e. they provide proof and you > can verify it, but really, why waste your time doing that extra work?) Frankly, the last bit is nonsense. If nothing else, consider the situation when somebody from UMN (which is a lot bigger than the group in question, but hell with it - somebody really from that group) posts an analysis of a real bug, along with a correct fix. With valid proof of correctness. What should we do? Leave the bug in place? Unattractive, to put it mildly. Write a fix and try to make it different from theirs? Not always feasible. Write a fix without looking at theirs and commit it? And if it happens to coincide with theirs, then what? FWIW, I do believe their claims that they tried to avoid introducing bugs and creating problems in general. So did RT[F]M, for that matter. However, the very nature of their "experiment"[1] required deflecting review. With obvious effects... [1] I won't go into its value, relevance of threat model, etc. at the moment - proper comments on that paper will take more time than I'm likely to have during the next couple of weeks.