From: Lokesh Gidra <lokeshgidra@google.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
SElinux list <selinux@vger.kernel.org>,
Kalesh Singh <kaleshsingh@google.com>,
Calin Juravle <calin@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Jeff Vander Stoep <jeffv@google.com>,
"Cc: Android Kernel" <kernel-team@android.com>
Subject: Re: [PATCH v3 1/1] selinux-testsuite: Add userfaultfd test
Date: Wed, 20 Jan 2021 15:02:52 -0800 [thread overview]
Message-ID: <CA+EESO6+kz3xS=064a2-Hxak2wWvVNYntrjZDhHTy4_e6uBtXA@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNtCV60-i9mFYudns+vfXYQDj1K5Rw4_Gz5r6fU0WCU2QQ@mail.gmail.com>
On Wed, Jan 20, 2021 at 2:39 PM Ondrej Mosnacek <omosnace@redhat.com> wrote:
>
> On Fri, Jan 8, 2021 at 3:38 AM Lokesh Gidra <lokeshgidra@google.com> wrote:
> >
> > Confirm SELinux policies are enforced on userfaultfd operations
> > via secure anon-inode interface.
> >
> > Signed-off-by: Lokesh Gidra <lokeshgidra@google.com>
> > ---
> > policy/Makefile | 4 +-
> > policy/test_userfaultfd.cil | 52 ++++++++++
> > policy/test_userfaultfd.te | 52 ++++++++++
> > tests/Makefile | 2 +-
> > tests/userfaultfd/Makefile | 5 +
> > tests/userfaultfd/test | 44 ++++++++
> > tests/userfaultfd/userfaultfd.c | 177 ++++++++++++++++++++++++++++++++
> > 7 files changed, 333 insertions(+), 3 deletions(-)
> > create mode 100644 policy/test_userfaultfd.cil
> > create mode 100644 policy/test_userfaultfd.te
> > create mode 100644 tests/userfaultfd/Makefile
> > create mode 100755 tests/userfaultfd/test
> > create mode 100644 tests/userfaultfd/userfaultfd.c
>
> Sorry for the long delay... This version is already almost there, I
> just had to fix some style issues and added checks so that the test is
> skipped on old systems (when <linux/usefaultfd.h> doesn't exist or
> userfaultfd(2) returns -ENOSYS).
>
Thanks so much for fixing these issues. And I apologize for missing them.
> You can review the changes at
> https://github.com/WOnder93/selinux-testsuite/commits/uffd3 and if you
> (or others) have no objections, I'll fold them into the patch and
> merge it with a note that it was edited by me.
LGTM
>
> If you prefer, you can also fetch the branch via the command-line:
> git fetch https://github.com/WOnder93/selinux-testsuite uffd3:uffd3
>
> Thank you for being patient with us :)
Thank you for the reviews. It was a very learning experience for me :)
>
> --
> Ondrej Mosnacek
> Software Engineer, Platform Security - SELinux kernel
> Red Hat, Inc.
>
next prev parent reply other threads:[~2021-01-21 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 2:38 [PATCH v3 1/1] selinux-testsuite: Add userfaultfd test Lokesh Gidra
2021-01-20 22:38 ` Ondrej Mosnacek
2021-01-20 23:02 ` Lokesh Gidra [this message]
2021-01-23 9:55 ` Ondrej Mosnacek
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='CA+EESO6+kz3xS=064a2-Hxak2wWvVNYntrjZDhHTy4_e6uBtXA@mail.gmail.com' \
--to=lokeshgidra@google.com \
--cc=calin@google.com \
--cc=jeffv@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=surenb@google.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).