From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: ltp-list@lists.sourceforge.net, James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>
Subject: Re: [LTP] regression: selinux testsuite broken since October
Date: Mon, 11 Jan 2010 15:31:00 -0600 [thread overview]
Message-ID: <20100111213100.GA28138@us.ibm.com> (raw)
In-Reply-To: <20100111210006.GA26554@us.ibm.com>
Quoting Serge E. Hallyn (serue@us.ibm.com):
> Quoting Serge E. Hallyn (serue@us.ibm.com):
> > Quoting Serge E. Hallyn (serue@us.ibm.com):
> > > Quoting Stephen Smalley (sds@tycho.nsa.gov):
> > > > On Mon, 2010-01-11 at 13:50 -0600, Serge E. Hallyn wrote:
> > > > > > Fails with:
> > > > > > cp: cannot stat
> > > > > > `/home/sds/ltp/testcases/kernel/security/selinux-testsuite/refpolicy/policy_files/generic/test_policy.*': No such file or directory
> > > > >
> > > > > You ran /home/sds/ltp/testscripts/test_selinux.sh, right?
> > > > >
> > > > > I think we are supposed to actually be running
> > > > > /opt/ltp/testscripts/test_selinux.sh. So then the first question for
> > > > > Garrett is how should we deduce /home/sds/ltp as $LTP_SRCDIR from a
> > > > > testscript? Or should the policy sources be copied into /opt?
> > > >
> > > > Ok, but regardless: the refpolicy Makefile is still broken.
> > >
> > > Yup.
> >
> > All right, baby-steps.
> >
> > The attached test_selinux.diff is not to be applied, but something
> > like it is needed. Should we have the ltp 'make install' fill in
> > TOP_SRCDIR in /opt/ltp/testscripts/test_selinux.sh? BTW, Garrett,
> > that is the issue I was saying is shared between test_selinux.sh
> > and some others including test_robind.sh. That's why I'm not just
> > sending a patch to make it work, bc i think we need more general
> > guidance.
> >
> > The second match makes the 'make load' part of test_selinux.sh
> > succeed on rhel5.4. Stephen, how does it do on fedora?
> >
> > After loading policy it fails to execute ltp-pan, but I figure let's
> > get policy loading working first.
All right well just doing
--- /root/ltp_cvs_orig/ltp/testscripts/test_selinux.sh 2009-05-19 05:39:11.000000000 -0400
+++ /opt/ltp/testscripts/test_selinux.sh 2010-01-11 16:26:12.000000000 -0500
@@ -115,7 +117,7 @@
SAVEBINTYPE=`ls -Zd $LTPROOT/testcases/bin | awk '{ print $4 }' | awk -F: '{ print $3 }'`
/usr/bin/chcon -t test_file_t $LTPROOT/testcases/bin
-$LTPROOT/pan/ltp-pan -S -a $LTPROOT/results/selinux -n ltp-selinux -l $LTPROOT/results/selinux.logfile -o $LTPROOT/results/selinux.outfile -p -f $LTPROOT/runtest/selinux
+$LTPROOT/bin/ltp-pan -S -a $LTPROOT/results/selinux -n ltp-selinux -l $LTPROOT/results/selinux.logfile -o $LTPROOT/results/selinux.outfile -p -f $LTPROOT/runtest/selinux
# cleanup before exiting
================================================================
in test_selinux.sh makes the testsuite mostly pass (test 39 fails, all
up to then pass)
Again this is on RHEL5.4.
-serge
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-01-11 21:31 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 15:25 [LTP] regression: selinux testsuite broken since October Stephen Smalley
2010-01-06 17:18 ` Serge E. Hallyn
2010-01-07 9:04 ` Garrett Cooper
2010-01-06 18:50 ` Serge E. Hallyn
2010-01-07 19:40 ` Stephen Smalley
2010-01-08 18:20 ` Garrett Cooper
2010-01-08 18:45 ` Stephen Smalley
2010-01-08 18:50 ` Stephen Smalley
2010-01-08 21:38 ` Garrett Cooper
2010-01-08 22:00 ` Stephen Smalley
2010-01-08 22:08 ` Garrett Cooper
2010-01-09 7:27 ` Garrett Cooper
2010-01-11 19:12 ` Stephen Smalley
2010-01-11 19:50 ` Serge E. Hallyn
2010-01-11 19:55 ` Stephen Smalley
2010-01-11 20:19 ` Serge E. Hallyn
2010-01-11 20:58 ` Serge E. Hallyn
2010-01-11 21:00 ` Serge E. Hallyn
2010-01-11 21:31 ` Serge E. Hallyn [this message]
2010-01-12 8:36 ` Garrett Cooper
2010-01-12 13:16 ` Stephen Smalley
2010-01-12 16:55 ` Garrett Cooper
2010-01-12 17:19 ` Garrett Cooper
2010-01-12 17:24 ` Garrett Cooper
2010-01-12 17:26 ` Garrett Cooper
2010-01-12 19:12 ` Stephen Smalley
2010-01-13 6:51 ` Garrett Cooper
2010-01-13 6:54 ` Garrett Cooper
2010-01-13 13:43 ` Stephen Smalley
2010-01-13 18:52 ` Garrett Cooper
2010-01-13 19:18 ` Stephen Smalley
2010-01-13 19:37 ` Garrett Cooper
2010-01-13 19:49 ` Stephen Smalley
2010-01-13 21:58 ` Garrett Cooper
2010-01-13 22:00 ` Serge E. Hallyn
2010-01-13 22:03 ` Stephen Smalley
2010-01-13 22:49 ` Garrett Cooper
2010-01-14 14:07 ` Stephen Smalley
2010-01-14 20:10 ` Garrett Cooper
2010-01-14 20:35 ` Stephen Smalley
2010-01-14 20:44 ` Stephen Smalley
2010-01-14 21:29 ` Garrett Cooper
2010-01-14 21:32 ` Garrett Cooper
2010-01-14 21:59 ` Stephen Smalley
2010-01-14 22:31 ` Stephen Smalley
2010-01-15 4:22 ` Garrett Cooper
2010-01-15 4:44 ` Garrett Cooper
2010-01-15 14:11 ` Stephen Smalley
2010-01-15 14:17 ` Stephen Smalley
2010-01-12 8:29 ` Garrett Cooper
2010-01-12 13:00 ` Stephen Smalley
2010-01-12 15:38 ` Serge E. Hallyn
2010-01-12 16:56 ` Garrett Cooper
2010-01-12 18:51 ` Stephen Smalley
2010-01-15 17:48 ` Garrett Cooper
2010-01-26 8:31 ` Garrett Cooper
2010-01-26 14:30 ` Stephen Smalley
2010-01-27 6:34 ` Garrett Cooper
2010-01-27 19:12 ` Stephen Smalley
2010-01-27 22:37 ` Garrett Cooper
2010-01-28 5:56 ` Garrett Cooper
2010-01-28 14:02 ` Stephen Smalley
2010-01-28 15:10 ` Garrett Cooper
2010-01-12 8:43 ` Garrett Cooper
2010-01-12 13:08 ` Stephen Smalley
2010-01-06 18:58 ` Serge E. Hallyn
2010-01-07 9:05 ` Garrett Cooper
2010-01-07 19:23 ` Stephen Smalley
2010-01-07 9:18 ` Garrett Cooper
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=20100111213100.GA28138@us.ibm.com \
--to=serue@us.ibm.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=sds@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