From: James Morris <jmorris@namei.org>
To: Paul Moore <paul@paul-moore.com>
Cc: "Kees Cook" <keescook@chromium.org>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Casey Schaufler" <casey@schaufler-ca.com>,
"John Johansen" <john.johansen@canonical.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Salvatore Mesoraca" <s.mesoraca16@gmail.com>
Subject: Re: [GIT PULL] blob-stacking updates for security-next
Date: Fri, 11 Jan 2019 09:00:08 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1901110858130.11115@namei.org> (raw)
In-Reply-To: <CAHC9VhSma5JCGf6Fi9NS1841kuWAKm4h9d7qW94yJNEO5t8oHg@mail.gmail.com>
On Thu, 10 Jan 2019, Paul Moore wrote:
> > Please test!
>
> While not exhaustive by any stretch of the imagination, you might want
> to throw the audit-testsuite at it too.
>
> * https://github.com/linux-audit/audit-testsuite
I'm seeing lots of failures with vanilla -rc1, probably much to do with my
kconfig:
Test Summary Report
-------------------
exec_name/test (Wstat: 0 Tests: 5 Failed: 2)
Failed tests: 4-5
filter_exclude/test (Wstat: 0 Tests: 21 Failed: 2)
Failed tests: 20-21
lost_reset/test (Wstat: 0 Tests: 5 Failed: 2)
Failed tests: 4-5
netfilter_pkt/test (Wstat: 0 Tests: 13 Failed: 13)
Failed tests: 1-13
syscalls_file/test (Wstat: 0 Tests: 3 Failed: 2)
Failed tests: 2-3
syscall_module/test (Wstat: 0 Tests: 6 Failed: 4)
Failed tests: 2-3, 5-6
syscall_socketcall/test (Wstat: 0 Tests: 3 Failed: 3)
Failed tests: 1-3
user_msg/test (Wstat: 0 Tests: 2 Failed: 2)
Failed tests: 1-2
Files=14, Tests=80, 16 wallclock secs ( 0.04 usr 0.02 sys + 2.21 cusr
0.60 csys = 2.87 CPU)
Result: FAIL
Failed 8/14 test programs. 30/80 subtests failed.
It would be good to have a defconfig to merge like with the SELinux
testsuite.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-01-10 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:35 [GIT PULL] blob-stacking updates for security-next Kees Cook
2019-01-10 20:34 ` James Morris
2019-01-10 21:21 ` Paul Moore
2019-01-10 22:00 ` James Morris [this message]
2019-01-10 22:39 ` Paul Moore
2019-01-11 18:24 ` James Morris
2019-01-11 10:38 ` Tetsuo Handa
2019-01-11 17:29 ` Casey Schaufler
2019-01-11 17:44 ` Kees Cook
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=alpine.LRH.2.21.1901110858130.11115@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=s.mesoraca16@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;
as well as URLs for NNTP newsgroup(s).