Spawned from crbug.com/858902 as it is related but different.


There are a lot of build failures with cheets_StartAndroid.stress: FAIL: Android did not boot!

Examples:

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941369727041519360

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941369731579338864

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941369720623870288

-----

From lpique@
It looks like arc-setup is now aborting. From var/log/android/android-run_oci.*


    [0710/111103:INFO:arc_setup.cc(1178)] Running !Chcon(kProcSecurityContext, arc_paths_->fake_kptr_restrict)...
    [0710/111103:ERROR:arc_setup_util.cc(693)] Could not label /run/arc/fake_kptr_restrict with u:object_r:proc_security:s0: Operation not supported
    [0710/111103:FATAL:arc_setup.cc(1178)] Check failed: !(!Chcon(kProcSecurityContext, arc_paths_->fake_kptr_restrict)). 
    /usr/sbin/arc_setup_wrapper.sh: line 12:  1847 Aborted                 (core dumped) 
    /usr/sbin/arc-setup --setup



----
From kroot@

It would be good to know what the mount flags for /run are at this point. ENOTSUP is returned if the filesystem doesn't support xattr or if the xattr prefix ("security." in this case) is not valid. There might be some kind of race condition where SELinux is not initialized by the time this code runs?