From: Paul Moore <pmoore@redhat.com>
To: David Miller <davem@davemloft.net>, selinux@tycho.nsa.gov
Cc: netdev@vger.kernel.org, omoris@redhat.com, pwouters@redhat.com
Subject: Re: [PATCH v3 0/2] Fix the SELinux dynamic network access controls
Date: Mon, 03 Jun 2013 11:11:38 -0400 [thread overview]
Message-ID: <8410550.MlrVbe5Pkl@sifl> (raw)
In-Reply-To: <20130531.173108.2170873839229968113.davem@davemloft.net>
On Friday, May 31, 2013 05:31:08 PM David Miller wrote:
> From: Paul Moore <pmoore@redhat.com>
> Date: Wed, 29 May 2013 13:36:18 -0400
>
> > Take #3 ... two changes here: the first is a simple reordering of the
> > two patches and the second is stripping the SELinux patch (2/2 in this
> > patchset) of everything but the bare bones changes needed to fix the
> > problem in the 3.10-rcX tree.
>
> Series applied, but longer term I'd like to see this handled by generation
> counts or similar during lookup time.
>
> Doing a GC every policy delete hurts policy delete performance, something
> we worked really hard to make as light weight as possible given the
> constraints.
Thanks for pulling in the fixes for 3.10-rcX.
I promise to take a look at changing our approach to detecting an active
labeled IPsec configuration for future releases. I need to cleanup our
labeled IPsec code anyway, it is in need of some TLC (you saw some of the
changes in the earlier version of this patchset).
--
paul moore
security and virtualization @ redhat
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <pmoore@redhat.com>
To: David Miller <davem@davemloft.net>, selinux@tycho.nsa.gov
Cc: netdev@vger.kernel.org, omoris@redhat.com, pwouters@redhat.com
Subject: Re: [PATCH v3 0/2] Fix the SELinux dynamic network access controls
Date: Mon, 03 Jun 2013 11:11:38 -0400 [thread overview]
Message-ID: <8410550.MlrVbe5Pkl@sifl> (raw)
In-Reply-To: <20130531.173108.2170873839229968113.davem@davemloft.net>
On Friday, May 31, 2013 05:31:08 PM David Miller wrote:
> From: Paul Moore <pmoore@redhat.com>
> Date: Wed, 29 May 2013 13:36:18 -0400
>
> > Take #3 ... two changes here: the first is a simple reordering of the
> > two patches and the second is stripping the SELinux patch (2/2 in this
> > patchset) of everything but the bare bones changes needed to fix the
> > problem in the 3.10-rcX tree.
>
> Series applied, but longer term I'd like to see this handled by generation
> counts or similar during lookup time.
>
> Doing a GC every policy delete hurts policy delete performance, something
> we worked really hard to make as light weight as possible given the
> constraints.
Thanks for pulling in the fixes for 3.10-rcX.
I promise to take a look at changing our approach to detecting an active
labeled IPsec configuration for future releases. I need to cleanup our
labeled IPsec code anyway, it is in need of some TLC (you saw some of the
changes in the earlier version of this patchset).
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2013-06-03 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 17:36 [PATCH v3 0/2] Fix the SELinux dynamic network access controls Paul Moore
2013-05-29 17:36 ` Paul Moore
2013-05-29 17:36 ` [PATCH v3 1/2] xfrm: force a garbage collection after deleting a policy Paul Moore
2013-05-29 17:36 ` Paul Moore
2013-05-29 17:36 ` [PATCH v3 2/2] selinux: fix the labeled xfrm/IPsec reference count handling Paul Moore
2013-05-29 17:36 ` Paul Moore
2013-06-01 0:31 ` [PATCH v3 0/2] Fix the SELinux dynamic network access controls David Miller
2013-06-03 15:11 ` Paul Moore [this message]
2013-06-03 15:11 ` Paul Moore
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=8410550.MlrVbe5Pkl@sifl \
--to=pmoore@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=omoris@redhat.com \
--cc=pwouters@redhat.com \
--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.