From: Stephen Smalley <sds@tycho.nsa.gov>
To: paul@paul-moore.com
Cc: selinux@vger.kernel.org, omosnace@redhat.com,
richard_c_haines@btinternet.com
Subject: Re: [PATCH v3 2/2] testsuite: add further nfs tests
Date: Wed, 5 Feb 2020 12:10:16 -0500 [thread overview]
Message-ID: <306f9a78-695c-dfd3-3524-3814997fac51@tycho.nsa.gov> (raw)
In-Reply-To: <20200130202239.11498-2-sds@tycho.nsa.gov>
On 1/30/20 3:22 PM, Stephen Smalley wrote:
> In addition to testing full NFS security labeling support,
> make sure that context mounts continue to work independent
> of whether the mount was exported with security_label, and
> add a simple test of the default NFS file labeling.
>
> With the previous changes, this completes addressing
> https://github.com/SELinuxProject/selinux-testsuite/issues/32
>
> Fixes: https://github.com/SELinuxProject/selinux-testsuite/issues/32
> Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
> ---
> v3 moves nfs.sh under tools/, updates README.md, and fixes nfs.sh for
> the relocation. As before, these patches depend on the previous one
> ("testsuite: enable running over labeled NFS") in order to allow the
> testsuite to pass on NFS mounts.
>
> README.md | 5 ++++-
> tools/nfs.sh | 38 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 42 insertions(+), 1 deletion(-)
Both are now applied.
[...]
next prev parent reply other threads:[~2020-02-05 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 20:22 [PATCH v3 1/2] testsuite: provide support for testing labeled NFS Stephen Smalley
2020-01-30 20:22 ` [PATCH v3 2/2] testsuite: add further nfs tests Stephen Smalley
2020-02-05 17:10 ` Stephen Smalley [this message]
2020-02-06 16:36 ` Stephen Smalley
2020-02-13 22:12 ` Paul Moore
2020-02-14 13:17 ` Stephen Smalley
2020-02-20 1:33 ` 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=306f9a78-695c-dfd3-3524-3814997fac51@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).