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

Issue 893063 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: Oct 22
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 891772



Sign in to add a comment

caroline-tot-chrome-information-pfq fails logging_UdevCrash.

Project Member Reported by sammiequon@chromium.org, Oct 8

Issue description

10/07 17:30:53.704 WARNI|              test:0606| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 464, in execute
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 91, in run_once
    self.run_crash_tests(['udev_report_atmel'], True)
  File "/usr/local/autotest/cros/crash/crash_test.py", line 697, in run_crash_tests
    getattr(self, '_test_' + test_name)()
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 87, in _test_udev_report_atmel
    exception=error.TestFail('No valid Atmel crash reports'))
  File "/usr/local/autotest/common_lib/utils.py", line 2756, in poll_for_condition
    value = condition()
  File "/usr/local/autotest/tests/logging_UdevCrash/logging_UdevCrash.py", line 24, in CheckAtmelCrashes
    filename)
TestFail: Crash report selinux_violation.20181008.003053.0.log has wrong name
 
Cc: vapier@chromium.org
+vapier

vapier: Any ideas why this might be crashing on caroline informational?
Blockedon: 891772
Components: OS>Systems>CrashReporting
Owner: f...@chromium.org
same as  issue 891772  prob

Comment 3 Deleted

Status: Assigned (was: Untriaged)
Status: Started (was: Assigned)
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 11

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/f23403776fe446efe4431198a90fcae2d26d949b

commit f23403776fe446efe4431198a90fcae2d26d949b
Author: Qijiang Fan <fqj@chromium.org>
Date: Thu Oct 11 15:55:53 2018

sepolicy: don't audit cros_udevd execute cros_crash_reporter_exec

It's expected behavior that cros_udevd may execute
cros_crash_reporter_exec. This audit is used to discover unexpected
behavior.

BUG= chromium:893063 
TEST=fake dev crash and dmesg

Change-Id: Ieb2247d59e83825a66a09f29a49c4d5f6f1ba77b
Reviewed-on: https://chromium-review.googlesource.com/1272897
Commit-Ready: Qijiang Fan <fqj@google.com>
Tested-by: Qijiang Fan <fqj@google.com>
Reviewed-by: Kenny Root <kroot@google.com>

[modify] https://crrev.com/f23403776fe446efe4431198a90fcae2d26d949b/sepolicy/policy/chromeos/cros_crash.te

Status: Fixed (was: Started)
Workarounded now by not printing udev exec crash_reporter into audit log.

Sign in to add a comment