From: Paul Moore <paul@paul-moore.com>
To: James Morris <jmorris@namei.org>
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: Thu, 10 Jan 2019 17:39:08 -0500 [thread overview]
Message-ID: <CAHC9VhSrj857SxvLx45O22pYbEf0SvWk+ZERTFJaoQkK6mcxmw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1901110858130.11115@namei.org>
On Thu, Jan 10, 2019 at 5:00 PM James Morris <jmorris@namei.org> wrote:
> 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:
FWIW, v5.0-rc1 passes on my test system. What userspace/distro are you running?
> It would be good to have a defconfig to merge like with the SELinux
> testsuite.
Yeah, the audit-testsuite is still pretty rough, there are lots of
things it needs.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-01-10 22:39 UTC|newest]
Thread overview: 8+ 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
2019-01-10 22:39 ` Paul Moore [this message]
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=CAHC9VhSrj857SxvLx45O22pYbEf0SvWk+ZERTFJaoQkK6mcxmw@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--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=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).