From: nicolas.iooss@m4x.org (Nicolas Iooss)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Fix minor typo in init.if
Date: Tue, 09 Sep 2014 00:46:53 +0200 [thread overview]
Message-ID: <540E31DD.5070506@m4x.org> (raw)
In-Reply-To: <20140908182740.GA24131@x220.network2>
2014-09-08 20:27 GMT+02:00 Dominick Grift:
> It seems that we have one or more commits that break reference policy since the last release
>
> I am trying to track down the culprits, it started after last release but before or during June 25th
>
> It is going to take time to track this down because build-testing reference policy is so slow.
>
> Looking forward to the day we fully moved to cil/secilc
>
Tonight I had the idea of using travis-ci.org to automate some kind of
testing. This free service can basically watch public Github
repositories and run tests after every commit. I ran tests in some
configurations [1] and every test case failed.
The monolithic build fails with [2]:
/usr/bin/checkpolicy -U deny policy.conf -o policy.26
/usr/bin/checkpolicy: loading policy configuration from policy.conf
checkpolicy: expand.c:721: role_fix_callback: Assertion `regular_role
!= ((void *)0) && regular_role->flavor == 0' failed.
make: *** [policy.26] Aborted
The modular build verification ("make validate") fails with [3]:
/usr/bin/semodule_expand tmp/test.lnk tmp/policy.bin
semodule_expand: expand.c:721: role_fix_callback: Assertion
`regular_role != ((void *)0) && regular_role->flavor == 0' failed.
make: *** [validate] Aborted
Is this assertion failure known? I did not take time to investigate
further but travis-ci may run an old version of the build toolchain (on
Ubuntu) which breaks the latest refpolicy.
Wkr,
Nicolas
[1]
https://travis-ci.org/fishilico/selinux-refpolicy-patched/builds/34760305
[2]
https://travis-ci.org/fishilico/selinux-refpolicy-patched/jobs/34760306#L202
[3]
https://travis-ci.org/fishilico/selinux-refpolicy-patched/jobs/34760307#L4227
next prev parent reply other threads:[~2014-09-08 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 21:29 [refpolicy] [PATCH] Fix minor typo in init.if Nicolas Iooss
2014-09-08 18:27 ` Dominick Grift
2014-09-08 22:46 ` Nicolas Iooss [this message]
2014-09-09 12:45 ` Christopher J. PeBenito
2014-09-09 13:28 ` Dominick Grift
2014-09-09 18:40 ` Christopher J. PeBenito
2014-09-09 18:51 ` Dominick Grift
2014-09-10 19:53 ` [refpolicy] Some already-fixed bugs (was: Re: [PATCH] Fix minor typo in init.if) Nicolas Iooss
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=540E31DD.5070506@m4x.org \
--to=nicolas.iooss@m4x.org \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.