selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>,
	selinux@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
	Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: [PATCH 2/2] selinux-testsuite: Add fs*(2) API filesystem tests
Date: Tue, 21 Jan 2020 13:56:59 -0500	[thread overview]
Message-ID: <bf9f4218-ee4d-ffc5-d0db-7f8f678d0090@tycho.nsa.gov> (raw)
In-Reply-To: <20200120111113.23349-3-richard_c_haines@btinternet.com>

On 1/20/20 6:11 AM, Richard Haines wrote:
> Test filesystem permissions using the fsopen(2), fsconfig(2), fsmount(2),
> fspick(2) and fsmount(2) api's introduced in kernel 5.2.
> 
> Also tests move_mount(2) using open_tree(2).
> 
> These tests use common code from tests/filesystem.
> 
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
<snip>
> diff --git a/tests/fs_filesystem/test b/tests/fs_filesystem/test
> new file mode 100755
> index 0000000..bda7fcf
> --- /dev/null
> +++ b/tests/fs_filesystem/test
> @@ -0,0 +1,833 @@
> +#!/usr/bin/perl
> +use Test::More;
<snip>
> +    # Set to '1' for testing 'hooks.c selinux_move_mount() FILE__MOUNTON'
> +    # Once kernel patch is mainline, add kernel version test.
> +    $test_move_mount = 0;
> +    if ($test_move_mount) {
> +        $test_count += 3;
> +    }

Wondering what we want the test above for test_move_mount to ultimately 
be.  It could be the first kernel version to include my fix.  That would 
avoid testsuite failures on kernels 5.2 through 5.5 assuming the fix is 
queued for 5.6.  On the other hand, it can be argued that the testsuite 
should fail on those kernels and the fix might end up going to stable 
and being back-ported to stable updates to those kernels, in which case 
testing those kernel versions may ultimately be useful.  Paul, what's 
your preference here?

  reply	other threads:[~2020-01-21 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 11:11 [PATCH 0/2] selinux-testsuite: Add fs*(2) API filesystem tests Richard Haines
2020-01-20 11:11 ` [PATCH 1/2] selinux-testsuite: Prepare for adding fs*(2) API tests Richard Haines
2020-01-24 15:12   ` Stephen Smalley
2020-01-20 11:11 ` [PATCH 2/2] selinux-testsuite: Add fs*(2) API filesystem tests Richard Haines
2020-01-21 18:56   ` Stephen Smalley [this message]
2020-01-24 15:13   ` Stephen Smalley
2020-01-24 19:17     ` Paul Moore
2020-01-24 19:25       ` Stephen Smalley
2020-01-24 19:41       ` 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=bf9f4218-ee4d-ffc5-d0db-7f8f678d0090@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=omosnace@redhat.com \
    --cc=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).