[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2187595.WquvNei6zx@sifl>
Date: Mon, 08 Jul 2013 12:30:17 -0400
From: Paul Moore <paul@...l-moore.com>
To: Waiman Long <waiman.long@...com>,
Eric Paris <eparis@...isplace.org>
Cc: Stephen Smalley <sds@...ho.nsa.gov>,
James Morris <james.l.morris@...cle.com>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org,
"Chandramouleeswaran, Aswin" <aswin@...com>,
"Norton, Scott J" <scott.norton@...com>, selinux@...ho.nsa.gov
Subject: Re: [PATCH 1/2 v5] SELinux: Reduce overhead of mls_level_isvalid() function call
On Friday, July 05, 2013 01:10:32 PM Waiman Long wrote:
> On 06/11/2013 07:49 AM, Stephen Smalley wrote:
> > On 06/10/2013 01:55 PM, Waiman Long wrote:
...
> >> Signed-off-by: Waiman Long <Waiman.Long@...com>
> >
> > Acked-by: Stephen Smalley <sds@...ho.nsa.gov>
>
> Thank for the Ack. Will that patch go into v3.11?
[NOTE: I add the SELinux list to the CC line, for future reference, be sure to
send your SELinux patches there.]
Your patch looked reasonable to me and Stephen ACK'd it so I went ahead and
pulled the 1/2 patch into my lblnet-next tree. It is probably an abuse of the
system, but as you noted it in the description, it does have an impact on
socket creation so it isn't completely unrelated ;)
If you don't want me to include your patch let me know and I'll drop it.
Now, being in my lblnet-next tree means pretty much nothing in terms of
actually getting upstream, but it will at least get the patch into tomorrow's
spin of the linux-next tree. I think is a good thing as it allows you to say
"my patch has been in linux-next for the past X weeks!" whenever Eric gets
around to merging patches again.
Here are the details for the lblnet-next tree:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_next
* http://git.infradead.org/users/pcmoore/lblnet-2.6_next
Also, a snapshot of what currently resides there:
Paul Moore (9):
selinux: fix problems in netnode when BUG() is compiled out
lsm: split the xfrm_state_alloc_security() hook implementation
selinux: cleanup and consolidate the XFRM alloc/clone/delete/free code
selinux: cleanup selinux_xfrm_policy_lookup() ...
selinux: cleanup selinux_xfrm_sock_rcv_skb() ...
selinux: cleanup some comment and whitespace issues in the XFRM code
selinux: cleanup selinux_xfrm_decode_session()
selinux: cleanup the XFRM header
selinux: remove the BUG_ON() from selinux_skb_xfrm_sid()
Waiman Long (1):
SELinux: Reduce overhead of mls_level_isvalid() function call
include/linux/security.h | 26 ++
security/capability.c | 15 +
security/security.c | 13 -
security/selinux/hooks.c | 11 +
security/selinux/include/xfrm.h | 45 ++--
security/selinux/netnode.c | 2
security/selinux/ss/ebitmap.c | 20 ++
security/selinux/ss/ebitmap.h | 2
security/selinux/ss/mls.c | 22 +-
security/selinux/ss/mls_types.h | 2
security/selinux/xfrm.c | 453 ++++++++++++++++---------------------
11 files changed, 291 insertions(+), 320 deletions(-)
--
paul moore
www.paul-moore.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists