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=-6.0 required=3.0 tests=BAYES_00,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 5EC01C433ED for ; Wed, 21 Apr 2021 12:19:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1A7BA61450 for ; Wed, 21 Apr 2021 12:19:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238905AbhDUMUD (ORCPT ); Wed, 21 Apr 2021 08:20:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:44766 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234573AbhDUMUD (ORCPT ); Wed, 21 Apr 2021 08:20:03 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7ECA9613E0; Wed, 21 Apr 2021 12:19:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1619007570; bh=L95QaJMrMeYMNbDPr8pjvWkKHVjgxGCPFXrCUXX8dN4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qsHvtM20kcZIl8G+2ULfzskF5Cf0Apte4j2pFt/1qPmEdARxGwRQ0+xxQzisTztU6 vuOeewCx3DG6PpLlp26hDZhxxzqmssComUxw5JnUh1zlXi9y0AjJa+IYZfiDEuQdaS z6FkCMyvw/809ZxAOFBlLn1yXbmWdOebvvd1jTtafnSb86qjSwqZQyHIIHXtlUFUYf l9EKm9Y5yUNsgRERm0WA4ATtEFd1bQKheeGmjktFZ+ffiC/jaRlU+xfA7jm8EGHVus T9aAZ2kZjVSDJ2mjgVVMpG1rZFuCSmQZfW+R7wgDpl5vaTlX17ItvdsZEZ05XZwUtO F3fTOc7K2xlqA== Date: Wed, 21 Apr 2021 15:19:26 +0300 From: Leon Romanovsky To: "Shelat, Abhi" Cc: Greg KH , Sudip Mukherjee , "J. Bruce Fields" , Aditya Pakki , Chuck Lever , Trond Myklebust , Anna Schumaker , "David S. Miller" , Jakub Kicinski , Dave Wysochanski , "linux-nfs@vger.kernel.org" , netdev , linux-kernel Subject: Re: [PATCH] SUNRPC: Add a check for gss_release_msg Message-ID: References: <20210407001658.2208535-1-pakki001@umn.edu> <20210420171008.GB4017@fieldses.org> <3B9A54F7-6A61-4A34-9EAC-95332709BAE7@northeastern.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3B9A54F7-6A61-4A34-9EAC-95332709BAE7@northeastern.edu> Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Wed, Apr 21, 2021 at 11:58:08AM +0000, Shelat, Abhi wrote: > >> > >>>> They introduce kernel bugs on purpose. Yesterday, I took a look on 4 > >>>> accepted patches from Aditya and 3 of them added various severity security > >>>> "holes". > >>> > >>> All contributions by this group of people need to be reverted, if they > >>> have not been done so already, as what they are doing is intentional > >>> malicious behavior and is not acceptable and totally unethical. I'll > >>> look at it after lunch unless someone else wants to do it… > >> > > > > Academic research should NOT waste the time of a community. > > If you believe this behavior deserves an escalation, you can contact the Institutional Review Board (irb@umn.edu) at UMN to investigate whether this behavior was harmful; in particular, whether the research activity had an appropriate IRB review, and what safeguards prevent repeats in other communities. The huge advantage of being "community" is that we don't need to do all the above and waste our time to fill some bureaucratic forms with unclear timelines and results. Our solution to ignore all @umn.edu contributions is much more reliable to us who are suffering from these researchers. Thanks