[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhTpsYDT5+CjdtiBmLMDEKV9fmGv+DyXVtUuja9d4i2ecg@mail.gmail.com>
Date: Tue, 12 Jun 2018 17:12:23 -0400
From: Paul Moore <paul@...l-moore.com>
To: James Morris <jmorris@...ei.org>, Joe Perches <joe@...ches.com>
Cc: Casey Schaufler <casey@...aufler-ca.com>,
John Johansen <john.johansen@...onical.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Eric Paris <eparis@...isplace.org>,
Kentaro Takeda <takedakn@...data.co.jp>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
selinux@...ho.nsa.gov
Subject: Re: [-next PATCH] security: use octal not symbolic permissions
On Tue, Jun 12, 2018 at 4:32 PM, James Morris <jmorris@...ei.org> wrote:
> On Mon, 11 Jun 2018, Casey Schaufler wrote:
>
>> If you want to break this up by security module I would take
>> the Smack part as soon as James does the tree update. If James
>> wants to take the whole thing at once you can add my:
>>
>> Acked-by: Casey Schaufler <casey@...aufler-ca.com>
>>
>> for the Smack changes.
>
> It's probably simplest for me to take them as one patch.
I would prefer if the SELinux changes were split into a separate
patch. I'm guessing John would probably want the same for the
AppArmor patches, but take his work for it, not mine.
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?
--
paul moore
www.paul-moore.com
Powered by blists - more mailing lists