From: Paul Moore <paul@paul-moore.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "Cédric Le Goater" <clg@kaod.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Richard Guy Briggs" <rgb@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: manual merge of the audit tree with the powerpc tree
Date: Thu, 16 Dec 2021 18:04:47 -0500 [thread overview]
Message-ID: <CAHC9VhTcV6jn4z7uGXZb=RZ5k7W4KW1vnoAUMHN6Zhkxsw1Xpg@mail.gmail.com> (raw)
In-Reply-To: <5f83d1fe-4e6e-1d08-b0c2-aec8ee852065@csgroup.eu>
On Thu, Dec 16, 2021 at 4:08 AM Christophe Leroy
<christophe.leroy@csgroup.eu> wrote:
> Thanks Cédric, I've now been able to install debian PPC32 port of DEBIAN
> 11 on QEMU and run the tests.
>
> I followed instructions in file README.md provided in the test suite.
> I also modified tests/Makefile to force MODE := 32
>
> I've got a lot of failures, am I missing some options in the kernel or
> something ?
>
> Running as user root
> with context root:::
> on system
While SELinux is not required for audit, I don't think I've ever run
it on system without SELinux. In theory the audit-testsuite shouldn't
rely on SELinux being present (other than the SELinux specific tests
of course), but I'm not confident enough to say that the test suite
will run without problem without SELinux.
If it isn't too difficult, I would suggest enabling SELinux in your
kernel build and ensuring the necessary userspace, policy, etc. is
installed. You don't need to worry about getting it all running
correctly; the audit-testsuite should pass with SELinux in permissive
mode.
If you're still seeing all these failures after trying that let us know.
> # Test 3 got: "256" (backlog_wait_time_actual_reset/test at line 151)
> # Expected: "0"
> # backlog_wait_time_actual_reset/test line 151 is: ok( $result, 0 );
> # Was an event found?
...
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2021-12-16 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:31 linux-next: manual merge of the audit tree with the powerpc tree Stephen Rothwell
2021-10-26 10:55 ` Michael Ellerman
2021-10-26 14:27 ` Paul Moore
2021-10-27 11:29 ` Michael Ellerman
2021-10-27 11:41 ` Christophe Leroy
2021-10-27 14:18 ` Paul Moore
2021-12-14 17:59 ` Christophe Leroy
2021-12-14 18:23 ` Paul Moore
2021-12-14 19:32 ` Christophe Leroy
2021-12-14 20:30 ` Cédric Le Goater
2021-12-16 9:08 ` Christophe Leroy
2021-12-16 23:04 ` Paul Moore [this message]
2021-12-17 14:11 ` Christophe Leroy
2022-01-12 17:19 ` Paul Moore
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='CAHC9VhTcV6jn4z7uGXZb=RZ5k7W4KW1vnoAUMHN6Zhkxsw1Xpg@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rgb@redhat.com \
--cc=sfr@canb.auug.org.au \
/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).