All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Eric Paris <eparis@redhat.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH v2 0/2] Fix the SELinux dynamic network access controls
Date: Fri, 24 May 2013 14:20:23 -0400	[thread overview]
Message-ID: <2018143.PsiGxnXVKA@sifl> (raw)
In-Reply-To: <20130524181430.24022.15997.stgit@localhost>

On Friday, May 24, 2013 02:16:16 PM Paul Moore wrote:
> A bump to v2 to incorporate Sergei's minor comment on the previous
> patchset.  I've also gone ahead and dropped the "RFC" from the
> patchset as I didn't see any significant comments/concerns from
> anyone.
> 
> ---
> 
> Paul Moore (2):
>       selinux: fix the labeled xfrm/IPsec reference count handling
>       xfrm: force a garbage collection after deleting a policy

Hi Dave, Eric,

I think we need to get this in for 3.10, assuming no objections from either 
one of you, who wants to pull it into their tree?

-Paul

P.S. Technically this could also be -stable material but I'm not pushing for 
that as this isn't really a panic issue, just a nuisance.

-- 
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: Eric Paris <eparis@redhat.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH v2 0/2] Fix the SELinux dynamic network access controls
Date: Fri, 24 May 2013 14:20:23 -0400	[thread overview]
Message-ID: <2018143.PsiGxnXVKA@sifl> (raw)
In-Reply-To: <20130524181430.24022.15997.stgit@localhost>

On Friday, May 24, 2013 02:16:16 PM Paul Moore wrote:
> A bump to v2 to incorporate Sergei's minor comment on the previous
> patchset.  I've also gone ahead and dropped the "RFC" from the
> patchset as I didn't see any significant comments/concerns from
> anyone.
> 
> ---
> 
> Paul Moore (2):
>       selinux: fix the labeled xfrm/IPsec reference count handling
>       xfrm: force a garbage collection after deleting a policy

Hi Dave, Eric,

I think we need to get this in for 3.10, assuming no objections from either 
one of you, who wants to pull it into their tree?

-Paul

P.S. Technically this could also be -stable material but I'm not pushing for 
that as this isn't really a panic issue, just a nuisance.

-- 
paul moore
security and virtualization @ redhat

  parent reply	other threads:[~2013-05-24 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 18:16 [PATCH v2 0/2] Fix the SELinux dynamic network access controls Paul Moore
2013-05-24 18:16 ` Paul Moore
2013-05-24 18:16 ` [PATCH v2 1/2] selinux: fix the labeled xfrm/IPsec reference count handling Paul Moore
2013-05-24 18:16   ` Paul Moore
2013-05-24 18:16 ` [PATCH v2 2/2] xfrm: force a garbage collection after deleting a policy Paul Moore
2013-05-24 18:16   ` Paul Moore
2013-05-24 18:20 ` Paul Moore [this message]
2013-05-24 18:20   ` [PATCH v2 0/2] Fix the SELinux dynamic network access controls Paul Moore
2013-05-28  6:31 ` David Miller

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=2018143.PsiGxnXVKA@sifl \
    --to=pmoore@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eparis@redhat.com \
    --cc=netdev@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.