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=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by aws-us-west-2-korg-lkml-1.web.codeaurora.org (Postfix) with ESMTP id 8542CC433EF for ; Wed, 13 Jun 2018 16:04:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 443CF208B2 for ; Wed, 13 Jun 2018 16:04:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 443CF208B2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=perches.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935973AbeFMQE0 (ORCPT ); Wed, 13 Jun 2018 12:04:26 -0400 Received: from smtprelay0123.hostedemail.com ([216.40.44.123]:41220 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S935404AbeFMQEY (ORCPT ); Wed, 13 Jun 2018 12:04:24 -0400 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id B61358368EE9; Wed, 13 Jun 2018 16:04:23 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: pigs08_7d4e10b62a036 X-Filterd-Recvd-Size: 3055 Received: from XPS-9350.home (unknown [47.151.150.235]) (Authenticated sender: joe@perches.com) by omf06.hostedemail.com (Postfix) with ESMTPA; Wed, 13 Jun 2018 16:04:20 +0000 (UTC) Message-ID: <00961ef3fb41930a3304da935f1f73ebe386e83c.camel@perches.com> Subject: Re: [-next PATCH] security: use octal not symbolic permissions From: Joe Perches To: Paul Moore Cc: James Morris , Casey Schaufler , John Johansen , Mimi Zohar , Dmitry Kasatkin , Stephen Smalley , Eric Paris , Kentaro Takeda , Tetsuo Handa , "Serge E. Hallyn" , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, selinux@tycho.nsa.gov Date: Wed, 13 Jun 2018 09:04:19 -0700 In-Reply-To: References: <1e91f8e10ce76d3208239b6b5899aab76d1543ff.1528743633.git.joe@perches.com> <3d890108a942b6a3fb9a5326501174af270707dc.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.28.1-2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-06-13 at 11:49 -0400, Paul Moore wrote: > On Tue, Jun 12, 2018 at 8:29 PM, Joe Perches wrote: > > On Tue, 2018-06-12 at 17:12 -0400, Paul Moore wrote: > > > Joe, in general I really appreciate the fixes you send, but these > > > patches that cross a lot of subsystem boundaries (this isn't the first > > > one that does this) causes unnecessary conflicts in -next and during > > > the merge window. Could you split your patches up from now on please? > > > > Sorry. No. Merge conflicts are inherent in this system. > > Yes, merge conflicts are inherent in this system when one makes a > single change which impacts multiple subsystems, e.g. changing a core > kernel function which is called by multiple subsystems. However, that > isn't what this patch does, it makes a number of self-contained > changes across multiple subsystems; there are no cross-subsystem > dependencies in this patch. You are increasing the likelihood of > conflicts for no good reason; that is why I'm asking you to split this > patch and others like it. No. History shows with high certainty that splitting patches like this across multiple subsystems of a primary subsystem means that the entire patchset is not completely applied. It's _much_ simpler and provides a generic mechanism to get the entire patch applied to send a single patch to the top level subsystem maintainer.