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 0E495C433B4 for ; Wed, 21 Apr 2021 17:35:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C765261458 for ; Wed, 21 Apr 2021 17:35:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244741AbhDURfr (ORCPT ); Wed, 21 Apr 2021 13:35:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:51278 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242842AbhDURfn (ORCPT ); Wed, 21 Apr 2021 13:35:43 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id F35A461459; Wed, 21 Apr 2021 17:35:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1619026509; bh=jsF90jMAoP9rK5ubz9IvKkVCBAZVLs25dg+tP0TLXVY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CI/LM0CuFrIxtemc7ItH2CTT5rer1JL8jQlmFFw0zQO98sG1dSJAHsiOCoi0fgmgP lRH2hvNnMgiD9yohzQHoR+PQQRvICsZcNQ/GjE50SdDeyzpBqouFisnzs1e97adR9l cRZFSIlL7+FCibqyAziu+I+IBU/btp5XJpAQPhL5v2IAw88co9nhh+CucTualNI1rL j1aVfUqIP+FEy7kc1TZAR/4rw/GvCNUZ6X0Br6y3Znde9OZyK0Ljza2CBq4gCwYjLh D4llnQ2T7kbGNqy9HYKO8+sEmU3tY3LNXrmy6OsfN3LRMRnkmSKBrS1aERhseka/oo etulTyRUw7+Og== Date: Wed, 21 Apr 2021 20:34:59 +0300 From: Mike Rapoport To: Theodore Ts'o Cc: Leon Romanovsky , Anna Schumaker , "J. Bruce Fields" , Greg KH , Aditya Pakki , Chuck Lever , Trond Myklebust , "David S. Miller" , Jakub Kicinski , Dave Wysochanski , Linux NFS Mailing List , netdev@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [PATCH] SUNRPC: Add a check for gss_release_msg Message-ID: References: <20210407001658.2208535-1-pakki001@umn.edu> <20210420171008.GB4017@fieldses.org> 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-kernel@vger.kernel.org On Wed, Apr 21, 2021 at 11:48:46AM -0400, Theodore Ts'o wrote: > On Wed, Apr 21, 2021 at 05:15:26PM +0300, Leon Romanovsky wrote: > > > This thread is the first I'm hearing about this. I wonder if there is > > > a good way of alerting the entire kernel community (including those > > > only subscribed to subsystem mailing lists) about what's going on? It > > > seems like useful information to have to push back against these > > > patches. Heh, I've got this information from google news feed on my phone :) > > IMHO, kernel users ML is good enough for that. > > The problem is that LKML is too high traffic for a lot of people to > want to follow. I think Leon meant kernel.org users ML (users@linux.kernel.org). Along with ksummut-discuss it'll reach most maintainers, IMHO. > There are some people who have used the kernel summit discuss list > (previously ksummit-discuss@lists.linux-foundation.org, now > ksummit@lists.linux.dev) as a place where most maintainers tend to be > subscribed, although that's not really a guarantee, either. (Speaking > of which, how to handle groups who submit patches in bad faith a good > Maintainer Summit topic for someone to propose...) -- Sincerely yours, Mike.