From: Paul Moore <paul@paul-moore.com>
To: Aaron Goidel <acgoide@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>,
Lukas Vrabec <lvrabec@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] selinux-testsuite: add tests for fsnotify
Date: Tue, 27 Aug 2019 13:14:25 -0400 [thread overview]
Message-ID: <CAHC9VhQqrgR7+qakF+bz-i0tL9fN0YQSSmXMyGL-TeLnkNpBkQ@mail.gmail.com> (raw)
In-Reply-To: <20190710133917.1188-1-acgoide@tycho.nsa.gov>
On Wed, Jul 10, 2019 at 9:40 AM Aaron Goidel <acgoide@tycho.nsa.gov> wrote:
>
> Added a suite to test permissions for setting inotify and fanotify watches
> on filesystem objects. Tests watch, watch_with_perm, and watch_reads permissions.
>
> Signed-off-by: Aaron Goidel <acgoide@tycho.nsa.gov>
> ---
> policy/Makefile | 4 ++
> policy/test_notify.te | 74 ++++++++++++++++++++++++
> tests/Makefile | 4 ++
> tests/notify/Makefile | 5 ++
> tests/notify/test | 101 +++++++++++++++++++++++++++++++++
> tests/notify/test_fanotify.c | 105 +++++++++++++++++++++++++++++++++++
> tests/notify/test_inotify.c | 43 ++++++++++++++
> 7 files changed, 336 insertions(+)
> create mode 100644 policy/test_notify.te
> create mode 100644 tests/notify/Makefile
> create mode 100755 tests/notify/test
> create mode 100644 tests/notify/test_fanotify.c
> create mode 100644 tests/notify/test_inotify.c
FYI, I'm still waiting on the new permissions to show up in the
Rawhide policy so I can test this and verify everything is working
correctly with a "released" policy.
I also had to perform a number of fixes to get 'make check-syntax' to
run cleanly.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-08-27 17:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 13:39 [PATCH] selinux-testsuite: add tests for fsnotify Aaron Goidel
2019-07-10 13:50 ` Aaron Goidel
2019-08-27 17:14 ` Paul Moore [this message]
2019-09-16 19:50 ` Stephen Smalley
2019-09-10 5:59 ` Dominick Grift
2019-09-10 12:26 ` Stephen Smalley
2019-09-10 14:15 ` Dominick Grift
2019-09-10 14:36 ` Dominick Grift
2019-09-10 14:40 ` Stephen Smalley
2019-09-10 14:54 ` Stephen Smalley
2019-09-10 14:59 ` Stephen Smalley
2019-09-10 15:02 ` [Non-DoD Source] " Stephen Smalley
2019-09-10 15:22 ` Dominick Grift
2019-09-10 16:25 ` Stephen Smalley
2019-09-10 16:32 ` Dominick Grift
2019-09-10 18:13 ` Stephen Smalley
2019-09-10 18:20 ` Dominick Grift
2019-09-10 19:45 ` Stephen Smalley
2019-09-10 19:55 ` Stephen Smalley
2019-09-10 20:00 ` Dominick Grift
2019-08-01 11:35 Aaron Goidel
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=CAHC9VhQqrgR7+qakF+bz-i0tL9fN0YQSSmXMyGL-TeLnkNpBkQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=acgoide@tycho.nsa.gov \
--cc=lvrabec@redhat.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).