From: Dan Noland <dan@starlab.io>
To: "selinux@vger.kernel.org" <selinux@vger.kernel.org>
Subject: Possible regression test failure?
Date: Sat, 4 May 2019 03:42:06 +0000 [thread overview]
Message-ID: <20190504034155.GA888@starlab.io> (raw)
- Hello -
I am running a CentOS (7.6.1810 Core) base system with a 4.19.0-x
kernel. I have a fresh clone of the selinux-testsuite from
github. Before invoking "make -C policy load" I am running only the
targeted policy in the enforcing mode. I am consistently seeing a
single failure in the mmap regression tests:
not ok 27
# Failed test 27 in ./mmap/test at line 143
# ./mmap/test line 143 is: ok($result);
Other than this one failure things seem to be OK according to the test
summary:
Test Summary Report
-------------------
mmap/test (Wstat: 0 Tests: 47 Failed: 1)
Failed test: 27
Files=51, Tests=520, 35 wallclock secs ( 0.11 usr 0.03 sys + 0.82
cusr 0.85 \
csys = 1.81 CPU)
Result: FAIL
Failed 1/51 test programs. 1/520 subtests failed.
The test in question is:
/bin/runcon -t test_no_map_t -- $basedir/mmap_file_shared $basedir/temp_file
Investigation indicates that the failure is caused by a bad (EACCES) open()
at mmap_file_shared.c:38
The AVC in the audit log shows that the { search } permission was
missing.
type=AVC msg=audit(1556938308.571:936): avc: denied { search } for
pid=7517 comm="mmap_file_share" name="vagrant" dev="dm-0" ino=81922
scontext=unconfined_u:unconfined_r:test_no_map_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=dir
permissive=0
type=SYSCALL msg=audit(1556938308.571:936): arch=c000003e syscall=2
success=no exit=-13 a0=7ffcc17da74a a1=2 a2=8 a3=7ffcc17d8d20 items=0
ppid=7512 pid=7517 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0
sgid=0 fsgid=0 tty=pts1 ses=4 comm="mmap_file_share"
exe="/home/vagrant/selinux-testsuite/tests/mmap/mmap_file_shared"
subj=unconfined_u:unconfined_r:test_no_map_t:s0-s0:c0.c1023 key=(null)
type=PROCTITLE msg=audit(1556938308.571:936):
proctitle=2F686F6D652F76616772616E742F73656C696E75782D7465737473756974652F74657374732F6D6D61702F6D6D61705F66696C655F736861726564002F686F6D652F76616772616E742F73656C696E75782D7465737473756974652F74657374732F6D6D61702F74656D705F66696C65
My understanding of the intent of this regression test is limited,
but I don't think this is an intended negative result.
Any wisdom on how I should understand and address this failure would
be gratefully received.
--
TY,
Dan Noland
next reply other threads:[~2019-05-04 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 3:42 Dan Noland [this message]
2019-05-04 18:00 ` Possible regression test failure? Ondrej Mosnacek
2019-05-06 17:14 ` Dan Noland
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=20190504034155.GA888@starlab.io \
--to=dan@starlab.io \
--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).