All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [GIT PULL] SELinux patches for 4.1
Date: Thu, 02 Apr 2015 17:18:30 -0400	[thread overview]
Message-ID: <3507958.kG4l2LfREA@sifl> (raw)
In-Reply-To: <alpine.LRH.2.11.1504022331430.4811@namei.org>

On Thursday, April 02, 2015 11:32:02 PM James Morris wrote:
> On Wed, 1 Apr 2015, Paul Moore wrote:
> > Hi James,
> > 
> > Five patches this time around: three patches to improve and enlarge the
> > the
> > avtab hash table, one to cleanup some MLS label import code, and one to
> > cleanup some of the avc code.  All of the patches are pretty small and
> > straightforward.  The two cleanup patches are trivially understandable and
> > the avtab code is well documented.
> > 
> > As usual, all patches pass the SELinux testsuite.
> > 
> > Enjoy,
> > -Paul
> > 
> > ---
> > 
> > The following changes since commit 
6436a123a147db51a0b06024a8350f4c230e73ff:
> >   selinux: fix sel_write_enforce broken return value
> >   
> >            (2015-03-25 16:55:06 -0400)
> > 
> > are available in the git repository at:
> >   git://git.infradead.org/users/pcmoore/selinux upstream
> > 
> > for you to fetch changes up to 9b43e04b188a1f715429604cca32b846e5a48cd2:
> >   Merge branch 'next' into upstream in preparation for v4.1
> >   (2015-04-01 22:24:51 -0400)
> 
> Is this branch downstream from my -next?

It should be, although likely an older version as I try not to pull unless 
necessary to resolve conflicts.  When I do a test merge into your next branch 
I see the following:

  #git pull selinux next
  From git://git.infradead.org/users/pcmoore/selinux
   * branch            next       -> FETCH_HEAD
  Auto-merging security/selinux/selinuxfs.c
  Merge made by the 'recursive' strategy.
   security/selinux/avc.c         |  6 ++--
   security/selinux/selinuxfs.c   |  2 +-
   security/selinux/ss/avtab.c    | 72 +++++++++++++++++++++++++++++---------
   security/selinux/ss/avtab.h    |  8 +++--
   security/selinux/ss/mls.c      | 10 ++----
   security/selinux/ss/services.c |  6 +---
   6 files changed, 68 insertions(+), 36 deletions(-)

The merge diffstat looks as I would expect, the only odd thing is selinuxfs.c, 
but it looks like that is simply because your next branch doesn't include the 
error code fix I sent you for v4.0:

  commit 6436a123a147db51a0b06024a8350f4c230e73ff
  Author: Joe Perches <joe@perches.com>
  Date:   Mon Mar 23 18:01:35 2015 -0700

    selinux: fix sel_write_enforce broken return value
    
    Return a negative error value like the rest of the entries in this  
    function.
    
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Joe Perches <joe@perches.com>
    Acked-by:  Stephen Smalley <sds@tycho.nsa.gov>
    [PM: tweaked subject line]
    Signed-off-by: Paul Moore <pmoore@redhat.com>

Are you asking because you ran into a problem, or just to check?

-- 
paul moore
security @ redhat

  reply	other threads:[~2015-04-02 21:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  2:49 [GIT PULL] SELinux patches for 4.1 Paul Moore
2015-04-02 12:32 ` James Morris
2015-04-02 21:18   ` Paul Moore [this message]
2015-04-03  2:45     ` James Morris
2015-04-03  9:04       ` Paul Moore
2015-04-03 15:07         ` James Morris
2015-04-03 22:22           ` Paul Moore
2015-04-04  0:49             ` James Morris
2015-04-04  2:36               ` Paul Moore
2015-04-05 23:14                 ` James Morris
2015-04-06 12:48                   ` Paul Moore
2015-04-06 14:04                     ` James Morris
2015-04-06 14:09                       ` James Morris
2015-04-07  0:43                       ` Paul Moore
2015-04-08 10:57                         ` James Morris
2015-04-08 11:04                           ` Paul Moore
2015-04-13  1:46                             ` James Morris
2015-04-23 22:06                               ` Paul Moore
2015-04-24  0:24                                 ` James Morris
2015-04-24 14:53                                   ` Paul Moore
2015-04-24 16:20                                     ` Casey Schaufler
2015-04-26 21:22                                       ` Paul Moore
2015-04-27  5:28                                         ` James Morris
2015-04-28 23:53                                           ` Mimi Zohar
2015-05-02 15:03                                             ` secilc bug Dominick Grift
2015-05-03 10:50                                               ` Dominick Grift
2015-05-04 15:19                                                 ` James Carter
2015-05-04 15:33                                                   ` Steve Lawrence
2015-05-04 15:44                                                     ` Dominick Grift
2015-05-04 15:46                                                       ` Dominick Grift
2015-05-04 15:37                                                   ` Dominick Grift
2015-08-03 19:21                                               ` Dominick Grift
2015-04-27  5:28                                     ` [GIT PULL] SELinux patches for 4.1 James Morris

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=3507958.kG4l2LfREA@sifl \
    --to=pmoore@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=selinux@tycho.nsa.gov \
    /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.