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: Wed, 6 Jan 2010 11:18:12 -0600 [thread overview]
Message-ID: <20100106171812.GA15444@us.ibm.com> (raw)
In-Reply-To: <1262791548.15424.31.camel@moss-pluto.epoch.ncsc.mil>
Quoting Stephen Smalley (sds@tycho.nsa.gov):
> It seems the Makefile rewrite last October broke the selinux testsuite.
> Is it unreasonable to expect that someone who rewrote the Makefile would
> actually try running the testsuite?
>
> Please, revert the changes or fix them.
>
> See testcases/kernel/security/selinux-testsuite/README for the
> instructions.
Seems I have a part in breakage as well. Here are patches to get the
execshare_parent to compile.
Now to get the policy to compile...
--- ltp-full-20091231.orig/testcases/kernel/security/selinux-testsuite/tests/execshare/selinux_execshare_parent.c 2009-11-03 15:07:35.000000000 -0500
+++ ltp-full-20091231/testcases/kernel/security/selinux-testsuite/tests/execshare/selinux_execshare_parent.c 2010-01-06 11:58:47.000000000 -0500
@@ -18,9 +18,12 @@
#include <selinux/selinux.h>
#include <selinux/context.h>
#include <sched.h>
+#include <test.h>
-int clone_fn(char **argv)
+int clone_fn(void *in)
{
+ char **argv = (char **) in;
+
execv(argv[3], argv+3);
perror(argv[3]);
return -1;
@@ -73,7 +76,7 @@ int main(int argc, char **argv)
fprintf(stderr, "%s: unable to set exec context to %s\n", argv[0], context_s);
exit(-1);
}
- pid = ltp_clone_quick(cloneflags | SIGCHLD, child_fn, argv);
+ pid = ltp_clone_quick(cloneflags | SIGCHLD, clone_fn, argv);
if (pid < 0) {
perror("clone");
exit(-1);
--- ltp-full-20091231.orig/testcases/kernel/security/selinux-testsuite/tests/execshare/Makefile 2009-10-09 13:55:51.000000000 -0400
+++ ltp-full-20091231/testcases/kernel/security/selinux-testsuite/tests/execshare/Makefile 2010-01-06 11:53:53.000000000 -0500
@@ -25,6 +25,6 @@ top_srcdir ?= ../../../../.
include $(top_srcdir)/include/mk/env_pre.mk
include $(abs_srcdir)/../Makefile.inc
-LDLIBS += -lselinux
+LDLIBS += -lselinux -lltp
include $(top_srcdir)/include/mk/generic_leaf_target.mk
------------------------------------------------------------------------------
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-06 17:18 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 [this message]
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
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=20100106171812.GA15444@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