From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 0/2] Labeled networking patches for 2.6.26
Date: Thu, 10 Apr 2008 18:12:36 -0400 [thread overview]
Message-ID: <200804101812.36542.paul.moore@hp.com> (raw)
In-Reply-To: <Xine.LNX.4.64.0804110802140.1313@us.intercode.com.au>
On Thursday 10 April 2008 6:04:32 pm James Morris wrote:
> On Thu, 10 Apr 2008, Paul Moore wrote:
> > Just a quick follow-up on testing, I've run this for a few hours on
> > two Fedora systems with both labeled and unlabeled IPsec in use
> > with SAs rekeying every 5 minutes and didn't notice anything evil.
> >
> > At this point I'd strip the "RFC" from the patchset and ask that
> > they be considered for inclusion in 2.6.26 assuming there are no
> > objections.
>
> I suggest pushing them via DaveM's tree, unless they depend on
> anything in my tree.
Okay. It sounds like DaveM is working through a backlog right now, if I
don't see them in his tree by next week I'll resubmit them.
Thanks.
--
paul moore
linux @ hp
next prev parent reply other threads:[~2008-04-10 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 20:50 [RFC PATCH v2 0/2] Labeled networking patches for 2.6.26 Paul Moore
2008-04-09 20:50 ` [RFC PATCH v2 1/2] NetLabel: Allow passing the LSM domain as a shared pointer Paul Moore
2008-04-10 22:06 ` James Morris
2008-04-09 20:50 ` [RFC PATCH v2 2/2] LSM: Make the Labeled IPsec hooks more stack friendly Paul Moore
2008-04-10 22:08 ` James Morris
2008-04-10 21:25 ` [RFC PATCH v2 0/2] Labeled networking patches for 2.6.26 Paul Moore
2008-04-10 22:04 ` James Morris
2008-04-10 22:12 ` Paul Moore [this message]
2008-04-10 22:47 ` David Miller
2008-04-13 2:18 ` 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=200804101812.36542.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).