From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH V2 0/2] selinux-testsuite: Add BPF tests
Date: Mon, 12 Aug 2019 18:34:41 -0400 [thread overview]
Message-ID: <CAHC9VhQG9K5Vf7njcZwefgLKhsBL_1xrGeJmGG7LBTa-wYPV4w@mail.gmail.com> (raw)
In-Reply-To: <28c7002e0482babaad5a56ea8ceeb26c11706364.camel@btinternet.com>
On Fri, Aug 9, 2019 at 12:51 PM Richard Haines
<richard_c_haines@btinternet.com> wrote:
> On Fri, 2019-08-09 at 11:27 -0400, Paul Moore wrote:
> > On Thu, Aug 1, 2019 at 7:22 AM Richard Haines
> > <richard_c_haines@btinternet.com> wrote:
> > > Patch 1 Runs basic checks for BPF with map_create, map_read,
> > > map_write,
> > > prog_load and prog_run permissions.
> > >
> > > Patch 2 Updates fdreceive to test BPF security_file_receive() path
> > > using
> > > the common BPF code in tests/bpf.
> > >
> > > If these are okay, I'll do the binder BPF tests for the
> > > security_binder_transfer_file() path.
>
> I've done the binder tests but will not send until you are full of
> happiness and light with these.
Several people have suggested I am full of various things, but oddly
enough no one has ever mentioned happiness and light ;)
> > Patch 1/2 seems to run fine on my test system, but I'm hitting some
> > errors with patch 2/2 ... although they appear to be gone now that I
> > run the test again to paste the error into my email :/
>
> Remember if running 2/2 locally after reboot, then need to set:
> setsebool allow_domain_fd_use=0
Playing with this some more I believe the problem I had last week was
due to not installing the necessary dependencies before building the
tests; let's attribute that to user error for the moment and move on.
We can revisit it if it keeps happening, but it looks to be okay now.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2019-08-12 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 11:12 [PATCH V2 0/2] selinux-testsuite: Add BPF tests Richard Haines
2019-08-09 15:27 ` Paul Moore
[not found] ` <28c7002e0482babaad5a56ea8ceeb26c11706364.camel@btinternet.com>
2019-08-12 22:34 ` Paul Moore [this message]
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=CAHC9VhQG9K5Vf7njcZwefgLKhsBL_1xrGeJmGG7LBTa-wYPV4w@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@vger.kernel.org \
/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).