public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [GIT] SELinux/IPsec: bugfix pull request
Date: Fri, 6 Oct 2006 13:21:09 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610061319170.6386@d.namei> (raw)

Hi Dave, please pull the following bugfix patches, for the IPsec/SELinux 
and related labeled network code.


The following changes since commit e77119c769b71c3f10b35d66988a3e279d30388c:
  James Morris:
        Merge ../../linux-2.6 into linus

are found in the git repository at:

  git://git.infradead.org/~jmorris/selinux-2.6.git

James Morris:
      IPsec: propagate security module errors up from flow_cache_lookup

paul.moore@hp.com:
      NetLabel: use SECINITSID_UNLABELED for a base SID

Venkat Yekkirala:
      IPsec: correct semantics for SELinux policy matching
      IPsec: fix handling of errors for socket policies

 include/linux/security.h        |   24 +++------
 include/net/flow.h              |    2 -
 include/net/xfrm.h              |    3 +
 net/core/flow.c                 |   42 +++++++++++-----
 net/ipv4/xfrm4_policy.c         |    2 -
 net/ipv6/xfrm6_policy.c         |    2 -
 net/key/af_key.c                |    5 --
 net/xfrm/xfrm_policy.c          |  101 +++++++++++++++++++++++++++++----------
 net/xfrm/xfrm_user.c            |    9 ---
 security/dummy.c                |    3 +
 security/selinux/include/xfrm.h |    3 +
 security/selinux/ss/services.c  |   29 +++--------
 security/selinux/xfrm.c         |   53 ++++++++++++++++----
 13 files changed, 171 insertions(+), 107 deletions(-)

-- 
James Morris
<jmorris@namei.org>

                 reply	other threads:[~2006-10-06 17:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.64.0610061319170.6386@d.namei \
    --to=jmorris@namei.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox