From: Stephen Smalley <sds@tycho.nsa.gov>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list <ltp-list@lists.sf.net>, Serge Hallyn <serge@hallyn.com>
Subject: Re: [LTP] selinux-testsuite has moved
Date: Tue, 26 Apr 2011 09:21:10 -0400 [thread overview]
Message-ID: <1303824070.4244.102.camel@moss-pluto> (raw)
In-Reply-To: <96AA5F80-E871-4368-BEB7-BC9FA24FFABD@gmail.com>
On Mon, 2011-04-25 at 12:38 -0700, Garrett Cooper wrote:
> On Apr 25, 2011, at 6:32 AM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > At present we see no benefit, only cost, to maintaining the selinux
> > testsuite in the ltp as it is regularly broken by unrelated changes
> > elsewhere in the ltp and as it is not truly integrated into the ltp (you
> > have to perform separate steps to build and run it). In comparison, we
> > don't have to worry about unrelated changes breaking the standalone
> > selinux testsuite, and it is certainly no harder to do this:
> >
> > git clone git://git.kernel.org/pub/scm/tests/selinux-testsuite
> > cd selinux-testsuite
> > sudo make test
> >
> > than to do this:
> >
> > git clone git://ltp.git.sourceforge.net/gitroot/ltp/ltp
> > cd ltp
> > make autotools
> > ./configure
> > make all
> > make install
> > cd testcases/kernel/security/selinux-testsuite
> > make all
> > make install
> > cd /opt/ltp
> > ./testscripts/test_selinux.sh
> >
> > If the selinux testsuite were fully integrated into the ltp (e.g. built
> > and run by default if SELinux is enabled on the system), then that might
> > be more worthwhile to keep it as part of the ltp. But in the 6 years
> > since it was added to the ltp, that hasn't happened.
>
> Do what's easiest for you guys to maintain upstream; what you suggested makes sense: pull from git and run selinux as-is. The twist I'm proposing here is as follows:
> 1. The selinux test suite needs to be made modular and portable. I'll provide you with autoconf/other patches sometime after I get back from vacation on friday.
> 2. I'll add logic to pull from git in ltp, which means the following: releases will come with the selinux test suite; archives and other non-release mechanisms won't. Thus, if you want to run the selinux testcases, you will need git, and will have to specify --with-selinux=yes when running configure, etc.
>
> Sound ok?
Not sure what modularity or portability problems you see in the
testsuite, but I think autotools would be overkill and just make
maintenance harder. If by modularity you mean the ability to run tests
individually, that is already possible, and if by portability you mean
the ability to build and run the tests on the various architectures, I
believe that also is already covered. We certainly don't have to
concern ourselves with portability to other OSes, as the selinux
testsuite is by definition specific to Linux.
--
Stephen Smalley
National Security Agency
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2011-04-26 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 13:08 [LTP] selinux-testsuite has moved Stephen Smalley
2011-04-22 20:43 ` Shubham Goyal
2011-04-25 13:32 ` Stephen Smalley
2011-04-25 19:20 ` Lucas Meneghel Rodrigues
2011-04-25 19:38 ` Garrett Cooper
2011-04-26 13:21 ` Stephen Smalley [this message]
2011-05-06 11:25 ` Cyril Hrubis
[not found] ` <1304686654.1821.14.camel@moss-pluto>
2011-05-11 12:39 ` Cyril Hrubis
2012-01-17 9:48 ` Jan Stancek
2012-01-18 13:16 ` Cyril Hrubis
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=1303824070.4244.102.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=ltp-list@lists.sf.net \
--cc=serge@hallyn.com \
--cc=yanegomi@gmail.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