Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp5632564pxb; Sun, 7 Nov 2021 16:50:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJyxpDD0IW6iMXsMRZwzXdN2P2ldFsj1GEins4P9m89iuhbsugwbmzvGU1mYncCYhjjYk7l5 X-Received: by 2002:a05:6402:27cd:: with SMTP id c13mr60854967ede.365.1636332625359; Sun, 07 Nov 2021 16:50:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636332625; cv=none; d=google.com; s=arc-20160816; b=TEM54Gb1pCeK5bLlLnf9R+0jLISovHXqaB1qvZ9iJc8b98Jqt9Pwl1pZbyWgv1S+kb rY+3KX4MN3yB0o7veIx4xxpsZSLjhRy/GGm5hYI0214MI4zn7Xk57inBNf562Zc0k4em GNtiKr3IP0t9aW5SQHhm/rCKH0djgHs7L+J0N+iYS9U+Qv0+4P47CXnXhIVQC2ToOvHv OdKdaYQqbUSBMIg1hR9TqtAaW9T9HaNogPFI6/1CcG5vcL4/hII1Y0S9nEDTHYyeTneT ZBnrL927oY063AriqlX5D5YSwuqOXEnDa0o8hR1IKHjy0FYUz1NNIoVZ2D1855ix+yTB CfIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=dqdME78YVA6aX0s6U5WuiTvDiXgwJjARSd92J434Jcg=; b=PWlERw2oyE2BNmOPmiePuUVh0FY8nM4SGR8TL8BMQTTv6nwkt2BRsGUrWMI6ovAEsH Ul5dEKJSbMREINsZNWDZsY/XCxYdo9bxFGbDFTFanfs3P+kULyCWNESJSdmKInMWr54E D1vAja54ql+PrwcHgivzTOBI+CCAP44044ZoK99XT+QxJB681k1SA5kjzOdT7/LvXqCo dHXYQLQvdp5zgb1MwylW6JyW0X1Yb5a0P7bFFoAmPsTGcGnk4gQfqL47zpRcXksjXQql P1p3VqpPc9Q/1l16q8ubV4B1/CHJ3gUDD0rxtT05nzfYSjL+vHPwW8Wtw+QILHEmfU1n gJzQ== 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 m6si31711517edd.87.2021.11.07.16.50.01; Sun, 07 Nov 2021 16:50:25 -0800 (PST) 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 S236259AbhKGTM4 (ORCPT + 99 others); Sun, 7 Nov 2021 14:12:56 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233008AbhKGTMx (ORCPT ); Sun, 7 Nov 2021 14:12:53 -0500 Received: from mail.monkeyblade.net (shards.monkeyblade.net [IPv6:2620:137:e000::1:9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52CFDC061570; Sun, 7 Nov 2021 11:10:10 -0800 (PST) Received: from localhost (225.159.143.150.dyn.plus.net [150.143.159.225]) by mail.monkeyblade.net (Postfix) with ESMTPSA id 345F74FE7B833; Sun, 7 Nov 2021 11:10:05 -0800 (PST) Date: Sun, 07 Nov 2021 19:09:59 +0000 (GMT) Message-Id: <20211107.190959.1432110661171124830.davem@davemloft.net> To: paul@paul-moore.com Cc: omosnace@redhat.com, netdev@vger.kernel.org, kuba@kernel.org, lucien.xin@gmail.com, richard_c_haines@btinternet.com, vyasevich@gmail.com, nhorman@tuxdriver.com, marcelo.leitner@gmail.com, linux-sctp@vger.kernel.org, selinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net] selinux: fix SCTP client peeloff socket labeling From: David Miller In-Reply-To: References: <20211104195949.135374-1-omosnace@redhat.com> X-Mailer: Mew version 6.8 on Emacs 27.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.monkeyblade.net [0.0.0.0]); Sun, 07 Nov 2021 11:10:07 -0800 (PST) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Paul Moore Date: Sun, 7 Nov 2021 09:12:57 -0500 > > When we change things as significantly as we are doing here, i.e. > shifting some of the labeling away from the endpoint to the > association, I much rather we do it as a chunk/patchset so that we can > review it in a consistent manner. Some of that has gone out the door > here because of what I view as recklessness on the part of the netdev > folks, but that doesn't mean we need to abandon all order. Let's get > all the fixes and repairs queued up in a single patchset so that we > can fully see what the end result of these changes are going to look > like. Further, I think it would be good if at least one of the > patches has a very clear explanation in the commit description (not > the cover letter, I want to see this in the git log) of what happens Cover letters show up in the merge commit log message for the patch series so they show up in the git commit log. Paul, please stop being so difficult and let's fix this. Thank you.