From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>,
selinux@vger.kernel.org
Subject: Re: [PATCH V3 0/1] selinux-testsuite: Add filesystem tests
Date: Mon, 13 Jan 2020 11:57:13 -0500 [thread overview]
Message-ID: <e0f09965-4e23-172f-568f-ea906672e5fd@tycho.nsa.gov> (raw)
In-Reply-To: <20200112192432.862800-1-richard_c_haines@btinternet.com>
On 1/12/20 2:24 PM, Richard Haines wrote:
> These tests should cover all the areas in selinux/hooks.c that touch
> the 'filesystem' class. Each hooks.c function is listed in the 'test'
> script as there are some permissions that are checked in multiple places.
>
> Tested on Fedora 31 and Rawhide (5.5 for the new watch perm).
>
> V3 Changes:
> 1) Lots of minor updates.
> 2) Add 'udevadm settle' as suggested by Ondrej to resolve udisks(8) issue.
> 3) Add stopping udisks(8) daemon as a '-d' option.
> 4) Add file quotaon test.
> 5) Add test for name type_transition rule.
> 6) Fix setfscreatecon(3) test to create a directory and check context.
> 7) Use kernel_dontaudit_setsched() as explained in [1].
>
> The only thing I have not done is cutting the clutter in the logs. Tried
> various things, all failed. Ideas !!!!
Looks like at least the y2038 warnings were removed in v5.4 so don't
need to worry about those. If they show up in a future kernel again, we
can avoid them by creating ext4 filesystems with inodes > 128 bytes ala
-I 256.
next prev parent reply other threads:[~2020-01-13 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 19:24 [PATCH V3 0/1] selinux-testsuite: Add filesystem tests Richard Haines
2020-01-12 19:24 ` [PATCH V3 1/1] " Richard Haines
2020-01-13 15:45 ` Stephen Smalley
2020-01-13 18:32 ` Richard Haines
2020-01-13 19:01 ` Stephen Smalley
2020-01-14 12:08 ` Richard Haines
2020-01-13 16:57 ` Stephen Smalley [this message]
2020-01-13 18:34 ` [PATCH V3 0/1] " Richard Haines
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=e0f09965-4e23-172f-568f-ea906672e5fd@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.