From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Joy Latten <latten@austin.ibm.com>,
David Miller <davem@davemloft.net>,
Eric Paris <eparis@redhat.com>,
netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
Venkat Yekkirala <vyekkirala@trustedcs.com>,
Steve G <linux_4ever@yahoo.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov
Subject: Re: LSPP kernels (was Re: [PATCH]: SAD sometimes has double SAs).
Date: Wed, 28 Mar 2007 12:36:57 -0400 [thread overview]
Message-ID: <200703281236.58222.paul.moore@hp.com> (raw)
In-Reply-To: <Line.LNX.4.64.0703281213060.2266@d.namei>
On Wednesday, March 28 2007 12:20:24 pm James Morris wrote:
> On Wed, 28 Mar 2007, Joy Latten wrote:
> > Eric, sorry as I know you already patched lspp kernel
> > for testing.
>
> I think it'd be better to have the lspp kernel join the upstream workflow
> process, rather than being a shortcut into RHEL.
>
> Please consider creating an lspp git tree (based off Linus' tree), then
> once patches there are tested and ready to submit upstream, post them here
> or selinux-list, where they can be reviewed and applied to either my or
> DaveM's git tree.
>
> From there, they'll be picked up in -mm for even wider testing then be
> merged into mainline as appropriate. Then, they can be incorporated into
> distro devel kernels when they update their kernels, or backported to
> stable distro kernels as already reviewed & tested upstream patches.
>
> If there are any objections, please respond.
I think the original intent of the LSPP kernel "series" was to test patches
before they were submitted to a wider audience (not too different from what
you are describing). Eric Paris became the LSPP/MLS group's Andrew Morton if
you will :)
However, for whatever reason, things appear to have stumbled a bit in recent
months and I think making an effort to move to a more standard approach based
on current kernel development would be a step in the right direction. This
would probably make backports a bit more difficult but Eric's a smart guy and
I'm sure he wouldn't mind :)
Does anyone have access to a public site we could use to host a git tree? If
no one has anything available (or is willing to maintain the tree) I might be
able to do something.
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2007-03-28 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 22:58 [PATCH]: SAD sometimes has double SAs Joy Latten
2007-03-23 23:27 ` David Miller
2007-03-26 21:34 ` Eric Paris
2007-03-26 21:48 ` David Miller
2007-03-27 1:04 ` Joy Latten
2007-03-28 15:15 ` Joy Latten
2007-03-28 16:20 ` LSPP kernels (was Re: [PATCH]: SAD sometimes has double SAs) James Morris
2007-03-28 16:36 ` Paul Moore [this message]
2007-03-28 19:12 ` David Miller
2007-03-28 16:49 ` Eric Paris
2007-03-28 17:11 ` James Morris
2007-03-28 19:13 ` [PATCH]: SAD sometimes has double SAs David Miller
2007-03-26 23:25 ` Joy Latten
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=200703281236.58222.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=latten@austin.ibm.com \
--cc=linux_4ever@yahoo.com \
--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).