From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>, Joe Perches <joe@perches.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [-next PATCH] security: use octal not symbolic permissions
Date: Tue, 12 Jun 2018 17:36:01 -0400 [thread overview]
Message-ID: <1528839361.3874.10.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <9ae2397b-ad11-d437-d0f4-4e4f0dff4ce9@canonical.com>
On Tue, 2018-06-12 at 14:29 -0700, John Johansen wrote:
> On 06/12/2018 02:12 PM, Paul Moore wrote:
> > On Tue, Jun 12, 2018 at 4:32 PM, James Morris <jmorris@namei.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@schaufler-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.
>
> yes that would be preferred
Agreed
>
> >
> > 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?
> >
>
> yeah splitting patches at subsystem boundaries is highly recommended.
Agreed
WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [-next PATCH] security: use octal not symbolic permissions
Date: Tue, 12 Jun 2018 17:36:01 -0400 [thread overview]
Message-ID: <1528839361.3874.10.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <9ae2397b-ad11-d437-d0f4-4e4f0dff4ce9@canonical.com>
On Tue, 2018-06-12 at 14:29 -0700, John Johansen wrote:
> On 06/12/2018 02:12 PM, Paul Moore wrote:
> > On Tue, Jun 12, 2018 at 4:32 PM, James Morris <jmorris@namei.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@schaufler-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.
>
> yes that would be preferred
Agreed
>
> >
> > 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?
> >
>
> yeah splitting patches at subsystem boundaries is highly recommended.
Agreed
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-12 21:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:01 [-next PATCH] security: use octal not symbolic permissions Joe Perches
2018-06-11 19:01 ` Joe Perches
2018-06-11 20:07 ` Casey Schaufler
2018-06-11 20:07 ` Casey Schaufler
2018-06-12 20:32 ` James Morris
2018-06-12 20:32 ` James Morris
2018-06-12 21:12 ` Paul Moore
2018-06-12 21:12 ` Paul Moore
2018-06-12 21:29 ` John Johansen
2018-06-12 21:29 ` John Johansen
2018-06-12 21:36 ` Mimi Zohar [this message]
2018-06-12 21:36 ` Mimi Zohar
2018-06-13 0:29 ` Joe Perches
2018-06-13 0:29 ` Joe Perches
2018-06-13 15:49 ` Paul Moore
2018-06-13 15:49 ` Paul Moore
2018-06-13 16:04 ` Joe Perches
2018-06-13 16:04 ` Joe Perches
2018-06-13 16:19 ` Paul Moore
2018-06-13 16:19 ` Paul Moore
2018-06-13 19:30 ` Joe Perches
2018-06-13 19:30 ` Joe Perches
2018-06-13 19:57 ` Paul Moore
2018-06-13 19:57 ` Paul Moore
2018-06-13 21:14 ` Casey Schaufler
2018-06-13 21:14 ` Casey Schaufler
2018-06-13 21:22 ` Paul Moore
2018-06-13 21:22 ` Paul Moore
2018-06-11 20:57 ` Tetsuo Handa
2018-06-13 15:19 ` Serge E. Hallyn
2018-06-13 15:19 ` Serge E. Hallyn
2018-06-13 23:49 ` Joe Perches
2018-06-13 23:49 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1528839361.3874.10.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=john.johansen@canonical.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.