From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov, eparis@redhat.com,
sds@tycho.nsa.gov, vyekkirala@TrustedCS.com
Subject: Re: [PATCH 0/2] [PATCH 0/2] Updated NetLabel/secid-reconciliation bits and a bugfix
Date: Wed, 04 Oct 2006 14:54:33 -0400 [thread overview]
Message-ID: <45240369.4030107@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610041439050.6196@d.namei>
James Morris wrote:
> On Wed, 4 Oct 2006, paul.moore@hp.com wrote:
>
>>This patchset includes an update to the NetLabel/secid-reconciliation patch,
>>replacing my "v3" patch from earlier this week, and a bugfix patch to cure a
>>race condition found during testing this week. The bugfix patch does not
>>rely on the secid patches and should be merged regardless as it fixes a bug
>>which has been around since the very first NetLabel patches (not sure why I
>>didn't see this sooner).
>
> So, patch 2/2 should go in on it's own against upstream? If so, in 5B
> future, please post such patches separately.
Yes, please commit patch 2/2 regardless as it fixes a bug which is not
dependent on any of the secid patches which are being discussed. My
apologies for including it in the same patchset, I'll be sure to split
it up next time.
> As for the rest of the network labeling, please work together with Venkat
> and the SELinux developers on a final patchset which meets all of the
> design goals and has been tested, with policy which has been merged
> upstream and is available via Fedora devel. Please keep the discussion
> going, but ensure that the final patchset for review and merge
> consideration is a complete set against the current git kernel coming from
> one person.
I'm trying :) When I posted the NetLabel secid support patch last week
I asked Venkat if he could merge it with the main secid patchset (due to
size and dependencies that seemed like the most reasonable course of
action). For reasons I'm not aware of he chose not to. As a result I
keep posting updated patches backed against Venkat's latest and
incorporating the latest feedback.
Venkat, can you please merge the latest my latest NetLabel secid support
patch in with your next release? If not, would you have a problem if I
pushed out a patchset which included your latest patches with the
NetLabel secid support patch and we used this patchset as the basis for
future work?
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2006-10-04 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 15:46 [PATCH 0/2] [PATCH 0/2] Updated NetLabel/secid-reconciliation bits and a bugfix paul.moore
2006-10-04 15:46 ` [PATCH v4 1/2] NetLabel: secid reconciliation support paul.moore
2006-10-04 15:46 ` [PATCH 2/2] NetLabel: fix a cache race condition paul.moore
2006-10-04 18:44 ` [PATCH 0/2] [PATCH 0/2] Updated NetLabel/secid-reconciliation bits and a bugfix James Morris
2006-10-04 18:54 ` Paul Moore [this message]
2006-10-04 22:56 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 19:11 Venkat Yekkirala
2006-10-04 19:42 ` 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=45240369.4030107@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.com \
/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).