Eric Blake wrote: > I'm seeing the following two failures on 'make check' on a > SELinux-enforcing Fedora 13 system:
Hi Eric, Thanks for the report. > FAIL: misc/runcon-no-reorder (exit: 1) ... > -runcon: failed to create security context: > unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023: Operation not > supported > +runcon: runcon may be used only on a SELinux kernel ... > I'm not sure why that failed during the test run, since on the command > line, I see: > > $ runcon unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 true -j > $ echo $? > 0 Odd indeed. Is there something unusual about your partition or system? That test does not fail for me on x86_64 Fedora 13 with SELinux in enforcing mode. > But since the test already maps other failures to a common message, > perhaps all that is needed is an additional mapping if 'Operation not > supported' results from the attempt? Before adding a work-around it'd be good to determine what is going wrong, especially since SELinux is implicated. > FAIL: misc/stat-mount (exit: 1) > =============================== ... > + stat_mnt=/shared/home > + test /shared = /shared/home > + fail=1 ... > Here, the failure is that I have /home bind-mounted on /shared/home, > and since I ran the test under /home, the mount location reported by > df is different than the one reported by stat -c%m. This is a new > test, and I'm not sure what to do about the issue (whether stat needs > fixing to deal with bind mounts, or whether the test is at fault). If there's a reliable mechanism to determine that there is a potentially interfering bind mount, I'd like to skip this test.
