selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Paul Moore <paul@paul-moore.com>,
	Ondrej Mosnacek <omosnace@redhat.com>,
	 SElinux list <selinux@vger.kernel.org>
Subject: selinux-testsuite nfs tests?
Date: Wed, 24 Jan 2024 13:42:00 -0500	[thread overview]
Message-ID: <CAEjxPJ4ev-pasUwGx48fDhnmjBnq_Wh90jYPwRQRAqXxmOKD4Q@mail.gmail.com> (raw)

So the recent discussion regarding questionable setting of
isec->sclass in inode_setxattr and inode_setsecurity that was
introduced by the labeled NFS support patch made me wonder about the
state of the selinux-testsuite nfs tests. Trying to run those on a
current kernel fails even before getting to the tests themselves
because the attempt to relabel the files to test_file_t fails with
Operation not supported errors. Anyone know when this last worked?

             reply	other threads:[~2024-01-24 18:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 18:42 Stephen Smalley [this message]
2024-01-24 20:13 ` selinux-testsuite nfs tests? Stephen Smalley
2024-01-24 23:59   ` Paul Moore
2024-01-25 13:32     ` Stephen Smalley
2024-01-25 14:25       ` Stephen Smalley
2024-01-25 14:52         ` Paul Moore
2024-01-25 15:14           ` Ondrej Mosnacek
2024-01-25 15:16             ` Paul Moore
2024-01-25 15:49               ` Stephen Smalley
2024-01-25 15:58                 ` Paul Moore
2024-01-25 15:59                 ` Stephen Smalley
2024-01-25 16:08                   ` Paul Moore
2024-01-26 10:11                     ` Ondrej Mosnacek
2024-05-02 19:18                       ` Stephen Smalley
2024-05-02 19:50                         ` Stephen Smalley
2024-05-02 19:54                           ` Stephen Smalley
2024-05-03  1:06                             ` 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=CAEjxPJ4ev-pasUwGx48fDhnmjBnq_Wh90jYPwRQRAqXxmOKD4Q@mail.gmail.com \
    --to=stephen.smalley.work@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.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).