From: Richard Haines <richard_c_haines@btinternet.com>
To: selinux@vger.kernel.org, paul@paul-moore.com, sds@tycho.nsa.gov
Cc: Richard Haines <richard_c_haines@btinternet.com>
Subject: [PATCH V5 0/3] selinux-testsuite: Add BPF tests
Date: Thu, 19 Sep 2019 18:46:52 +0100 [thread overview]
Message-ID: <20190919174655.17348-1-richard_c_haines@btinternet.com> (raw)
Patch 1 Runs basic checks for BPF with map_create, map_read, map_write,
prog_load and prog_run permissions.
V2 Change - Split BPF code into bpf_common.c for others to use.
V3 Changes - Correct style, Fix typos
V4 Changes - Fixes as discussed in [1]
V5 Changes - Update build BPF Linux version to 4.15, rework bpf_common.c
bpf_setrlimit() to use smaller RLIMIT_MEMLOCK limit.
Patch 2 Updates fdreceive to test BPF security_file_receive() path using
the common BPF code in tests/bpf.
V2 Change - Added to use tests/bpf/bpf_common.c for BPF tests.
V3 Changes - Run tests under tests/bpf not tests/fdreceive, fix typos.
V4 Changes - Update to work with changes in [1]
V5 Change - Remove check if fdreceive BPF enabled
Patch 3 - Updates Binder to test BPF path security_binder_transfer_file()
V4 Change - New patch
V5 Change - Remove check if Binder BPF enabled
[1] https://lore.kernel.org/selinux/19b043bc4d5efbf2f1994958c0a74709a34e3ad0.camel@btinternet.com/
Richard Haines (3):
selinux-testsuite: Add BPF tests
selinux-testsuite: Add BPF support to fdreceive test
selinux-testsuite: Add BPF support to binder test
README.md | 4 +-
defconfig | 5 +
policy/Makefile | 4 +
policy/test_binder_bpf.te | 73 +++++++++++++
policy/test_bpf.te | 77 +++++++++++++
policy/test_fdreceive_bpf.te | 60 ++++++++++
tests/Makefile | 7 ++
tests/binder/Makefile | 5 +
tests/binder/binder_common.c | 10 +-
tests/binder/binder_common.h | 17 ++-
tests/binder/client.c | 28 ++++-
tests/binder/manager.c | 2 +-
tests/binder/service_provider.c | 118 +++++++++++++++-----
tests/bpf/.gitignore | 2 +
tests/bpf/Makefile | 17 +++
tests/bpf/bpf_common.c | 69 ++++++++++++
tests/bpf/bpf_common.h | 34 ++++++
tests/bpf/bpf_test.c | 77 +++++++++++++
tests/bpf/test | 187 ++++++++++++++++++++++++++++++++
tests/fdreceive/Makefile | 14 ++-
tests/fdreceive/client.c | 93 ++++++++++++++--
21 files changed, 850 insertions(+), 53 deletions(-)
create mode 100644 policy/test_binder_bpf.te
create mode 100644 policy/test_bpf.te
create mode 100644 policy/test_fdreceive_bpf.te
create mode 100644 tests/bpf/.gitignore
create mode 100644 tests/bpf/Makefile
create mode 100644 tests/bpf/bpf_common.c
create mode 100644 tests/bpf/bpf_common.h
create mode 100644 tests/bpf/bpf_test.c
create mode 100755 tests/bpf/test
--
2.21.0
next reply other threads:[~2019-09-19 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 17:46 Richard Haines [this message]
2019-09-19 17:46 ` [PATCH V5 1/3] selinux-testsuite: Add BPF tests Richard Haines
2019-09-19 17:46 ` [PATCH V5 2/3] selinux-testsuite: Add BPF support to fdreceive test Richard Haines
2019-09-19 17:46 ` [PATCH V5 3/3] selinux-testsuite: Add BPF support to binder test Richard Haines
2019-09-19 20:15 ` Stephen Smalley
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=20190919174655.17348-1-richard_c_haines@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--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).