From: Venkat Yekkirala <vyekkirala@TrustedCS.com>
To: selinux@tycho.nsa.gov
Cc: redhat-lspp@redhat.com, jmorris@namei.org, sds@tycho.nsa.gov,
paul.moore@hp.com, eparis@redhat.com, jbrindle@tresys.com
Subject: [PATCH 0/1] selinux: secid reconciliation fixes V01: Intro
Date: Mon, 09 Oct 2006 07:21:35 -0500 [thread overview]
Message-ID: <452A3ECF.5030105@trustedcs.com> (raw)
This patchset is relative to davem's net-2.6 git tree as of a few weeks back,
and is an incremental fix to the secid-reconciliation patch series plus
the ipsec leak patches.
This patchset includes the fix sent out this past Friday night.
This patchset is more immediately intended for the kernels undergoing
LSPP certification, but needs to be reviewed for very-near-future
upstreaming into 2.6.19.
Paul, if you could respin your patchset relative to this one I would
appreciate it. While doing so, can you look for NetLabel only when
there's no xfrm label on a packet, since we now know that using both
is redundant? This way we don't have to worry about NetLabel code
bugs/side effects when someone is using just xfrm. Thanks.
--
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.
next reply other threads:[~2006-10-09 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 12:21 Venkat Yekkirala [this message]
2006-10-09 12:40 ` [PATCH 0/1] selinux: secid reconciliation fixes V01: Intro Joshua Brindle
2006-10-09 14:28 ` Paul Moore
2006-10-09 14:33 ` James Morris
2006-10-09 16:27 ` Paul Moore
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 13:56 Venkat Yekkirala
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=452A3ECF.5030105@trustedcs.com \
--to=vyekkirala@trustedcs.com \
--cc=eparis@redhat.com \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.