New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 807012 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

chromeos-4.14: cheets_SELinuxTest fails with Unexpected label

Project Member Reported by groeck@chromium.org, Jan 29 2018

Issue description

trybots with chromeos-4.14 fail with the following error.

01/19 19:55:36.231 WARNI|               arc:0451| Iteration 1 failed, taking a screenshot.
01/19 19:55:36.573 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 495, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/cheets_SELinuxTest/cheets_SELinuxTest.py", line 445, in run_once
    self._check_sys_devices_system_cpu_labels()
  File "/usr/local/autotest/tests/cheets_SELinuxTest/cheets_SELinuxTest.py", line 326, in _check_sys_devices_system_cpu_labels
    check_top_dir=False)
  File "/usr/local/autotest/tests/cheets_SELinuxTest/cheets_SELinuxTest.py", line 43, in _check_file_labels_recursively
    _assert_eq(expected, label, 'label for %s' % path)
  File "/usr/local/autotest/tests/cheets_SELinuxTest/cheets_SELinuxTest.py", line 29, in _assert_eq
    .format(msg, expected, actual))
TestFail: Unexpected label for /sys/devices/system/cpu/cpu1/power/pm_qos_resume_latency_us: Expected: u:object_r:sysfs:s0, Actual: u:object_r:sysfs_devices_system_cpu:s0

This is observed pretty much on all platforms running ARC+; actively seen with both release and paladin trybot runs on banon, celes, wizpig, cave, caroline, chell, lars, eve, and reef.

 

Comment 1 by uekawa@google.com, Jan 30 2018

Cc: jhorwich@chromium.org yoshiki@chromium.org
+constables

Cc: yusukes@chromium.org
+yusukes: May have idea since he's working on SELinux.
As I saw the several recent builds on eve-release and reef-release, I can't find the failure of cheets_SELinuxTest. Maybe this is already fixed?

Comment 4 by groeck@chromium.org, Jan 30 2018

#3: I can't comment on reef/eve builds with chromeos-4.4 (which is the shipping release); as mentioned, this is seen when running trybots with chromeos-4.14. 

Maybe a bug was fixed in chromeos-4.4, but I don't find a related bug entry, and I don't see a problem with the actual attributes in the kernel. I also found that Android does set some labels to sysfs_devices_system_cpu, but I have no idea what is expected.

I filed the bug since there is reason to believe that this problem will also be seen when we start testing systems which _will_ ship with chromeos-4.14.

Cc: lhchavez@chromium.org
@ comment 3 - note this is with a newer kernel (4.14). Luis mentioned we might need to add some new files to chromeos_file_contexts for the newer kernel

Comment 6 by uekawa@chromium.org, Jan 31 2018

Cc: kroot@chromium.org
Components: Platform>Apps>ARC
Cc: -lhchavez@chromium.org

Sign in to add a comment