From: Richard Haines <richard_c_haines@btinternet.com>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: selinux@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC V2 PATCH 1/2] selinux-testsuite: Use native filesystem for tests - Part 1
Date: Tue, 25 Feb 2020 16:38:30 +0000 [thread overview]
Message-ID: <80909c6b15e1816ad7857f759f9855e2fd70af71.camel@btinternet.com> (raw)
In-Reply-To: <CAEjxPJ6cMrqbpqCxsog9HOY98awjDMPJ7UpNfCS99_pViwv1AQ@mail.gmail.com>
On Tue, 2020-02-25 at 11:26 -0500, Stephen Smalley wrote:
> On Tue, Feb 25, 2020 at 11:18 AM Stephen Smalley
> <stephen.smalley.work@gmail.com> wrote:
> > If you just ran the nametrans tests in the host filesystem rather
> > than
> > in the separate mount, I think it would work.
> > This would require adjusting the type_transition rules however to
> > reflect the actual parent directory type (probably test_file_t).
>
> I just confirmed manually that name-based type transitions work over
> labeled NFS. The problem is just that your existing type_transition
> rules aren't matching on the parent directory type because you are
> creating the files in a separate mount that is using one or more
> context= options rather than in the base mount itself, unlike the
> setfscreatecon() tests above them that just operate within the host
> filesystem.
Thanks, Ill fix
next prev parent reply other threads:[~2020-02-25 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 14:15 [RFC V2 PATCH 0/2] selinux-testsuite: Use native filesystem for tests Richard Haines
2020-02-24 14:15 ` [RFC V2 PATCH 1/2] selinux-testsuite: Use native filesystem for tests - Part 1 Richard Haines
2020-02-24 21:17 ` Stephen Smalley
2020-02-25 16:04 ` Richard Haines
2020-02-25 16:18 ` Stephen Smalley
2020-02-25 16:26 ` Stephen Smalley
2020-02-25 16:38 ` Richard Haines [this message]
2020-02-24 14:15 ` [RFC V2 PATCH 2/2] selinux-testsuite: Use native filesystem for tests - Part 2 Richard Haines
2020-02-24 16:24 ` [RFC V2 PATCH 0/2] selinux-testsuite: Use native filesystem for tests Stephen Smalley
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=80909c6b15e1816ad7857f759f9855e2fd70af71.camel@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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).