selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Haines <richard_c_haines@btinternet.com>
To: Paul Moore <paul@paul-moore.com>
Cc: selinux@vger.kernel.org, tkjos@google.com
Subject: Re: [PATCH 1/1] selinux-testsuite: Update binder test applications
Date: Wed, 10 Apr 2019 18:04:44 +0100	[thread overview]
Message-ID: <a1869fe6f41148a956ff902d7077356fc729b28b.camel@btinternet.com> (raw)
In-Reply-To: <CAHC9VhTTeetqR03+zaV0d_2rdHr4r6eKnqKNrXO6k9O7+tz=gQ@mail.gmail.com>

On Wed, 2019-04-10 at 11:35 -0400, Paul Moore wrote:
> On Wed, Apr 3, 2019 at 8:43 AM Richard Haines
> <richard_c_haines@btinternet.com> wrote:
> > Replace binder_test.c with separate manager, client and service
> > provider.
> > This works in the same way as a service provider/client interacts
> > with a service manager in the Android world. It passes the service
> > providers binder file descriptor to the client for the impersonate
> > permission check.
> > 
> > Also added tests for Dynamically Allocated Binder Devices and
> > passing
> > the sender SELinux security context on binder transactions.
> > 
> > Note that the tests require a minimum kernel of 4.16, else some
> > tests may
> > fail. To run successfully the "binder: Add thread->process_todo
> > flag"
> > patch may be required that is available from:
> > https://lore.kernel.org/patchwork/patch/851324/
> > This patch has been backported to some earlier kernels.
> > 
> > Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> > ---
> >  defconfig                       |   3 +
> >  policy/test_binder.te           | 176 ++++----
> >  tests/binder/.gitignore         |   6 +-
> >  tests/binder/Makefile           |  13 +-
> >  tests/binder/binder_common.c    | 155 +++++++
> >  tests/binder/binder_common.h    |  37 ++
> >  tests/binder/check_binder.c     |  27 +-
> >  tests/binder/check_binderfs.c   |  53 +++
> >  tests/binder/client.c           | 450 ++++++++++++++++++++
> >  tests/binder/manager.c          | 362 ++++++++++++++++
> >  tests/binder/service_provider.c | 404 ++++++++++++++++++
> >  tests/binder/test               | 257 ++++++++++--
> >  tests/binder/test_binder.c      | 705 ----------------------------
> > ----
> >  13 files changed, 1785 insertions(+), 863 deletions(-)
> >  create mode 100644 tests/binder/binder_common.c
> >  create mode 100644 tests/binder/binder_common.h
> >  create mode 100644 tests/binder/check_binderfs.c
> >  create mode 100644 tests/binder/client.c
> >  create mode 100644 tests/binder/manager.c
> >  create mode 100644 tests/binder/service_provider.c
> >  delete mode 100644 tests/binder/test_binder.c
> 
> Hi Richard,
> 
> Welcome back :)
> 
> I had hoped to spend some time reading up on Binder so I could give
> this a proper review, but that hasn't happened so I'm inclined to
> merge it, assuming it works on my test system.  However, considering
> your comment about this not working on kernel's older than 4.16, I
> think we should probably add some checks to only run this test on
> systems with the appropriate kernel support.
> 
> If you look at tests/Makefile you will see a number of distro
> specific
> test list modifications, and there is even an example of checking the
> kernel version (search for "kvercmp" in the Makefile).  I would
> suggest a simple check to make sure the kernel is at least v4.16, and
> if we find distro specific support (e.g. a particular distro
> backported the listed patch) we can always add an exception for that
> distro.
> 
> How does that sound?

There are tests for the OS in the 'test' script already. I guess you
need to check if these are okay, as I check if < 4.16 and if so print
message saying if fail check for the patch.

I'm not sure this will get to the list as I appear to be black-balled.
I did send a cover letter with this patch + another one regarding
running SCTP on < 4.20.17. I sent email to 
owner-selinux@vger.kernel.org but not heard anything yet.

Cover Letter:
Subject: [PATCH 0/1] selinux-testsuite: Update binder test applications

The Binder tests have been rewritten to support the new Dynamically
Allocated Binder Devices and passing the sender SELinux security
context on binder transactions.

They have been tested on f29 and rawhide with the following kernels
from kernel.org:
mainline: 5.1-rc3
longterm: 4.19.32
longterm: 4.14.109

As noted in the main patch, the tests require a minimum kernel of 4.16,
else some tests may fail (tests 4 & 7). To run successfully the
4.14.109 kernel was patched with: "binder: Add thread->process_todo
flag" available from:
https://lore.kernel.org/patchwork/patch/851324/

I found that on slow systems using 4.14.109, all tests would pass,
however when testing on a faster system they would fail. Once patched,
worked fine.

Any testing feedback gratefully received.

Richard

> 


  reply	other threads:[~2019-04-13 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 12:26 [PATCH 1/1] selinux-testsuite: Update binder test applications Richard Haines
2019-04-10 15:35 ` Paul Moore
2019-04-10 17:04   ` Richard Haines [this message]
2019-04-10 23:43     ` Paul Moore
2019-04-11 11:48       ` Richard Haines
2019-04-11 22:07         ` Paul Moore
2019-04-12 14:46           ` Paul Moore
2019-04-12 16:37             ` Richard Haines
2019-04-12 19:20               ` Paul Moore
2019-04-12 19:28                 ` Stephen Smalley
2019-04-12 19:31                 ` Dominick Grift
2019-04-12 22:02                   ` Paul Moore
2019-04-17 15:27                     ` Paul Moore

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=a1869fe6f41148a956ff902d7077356fc729b28b.camel@btinternet.com \
    --to=richard_c_haines@btinternet.com \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=tkjos@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).