Message ID | 20200112192432.862800-1-richard_c_haines@btinternet.com (mailing list archive) |
---|---|
Headers | show |
Series | selinux-testsuite: Add filesystem tests | expand |
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.
On Mon, 2020-01-13 at 11:57 -0500, Stephen Smalley wrote: > 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. I'll add -I 256 in v4 just in case >