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

Issue 869971 link

Starred by 1 user
Status: Fixed
Owner:
█ samanthamiller@chromium.org
Last visit > 30 days ago
Closed: Aug 3
Cc:
xzhou@chromium.org
jclinton@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

fizz: changing crossystem flags leads to flashrom coredump and mosys errors

Project Member Reported by apronin@chromium.org, Aug 1 
On fizz on M70-10926.0.0:

1) Changing flags in crossystem leads to:
# crossystem dev_boot_usb=1
Child process did not exit normally.
Failed to read VBNV from flash.
Application error: Subcommand execution finished with error -1
waitpid() or mosys error

And /var/log/messages contains
2018-08-01T11:07:57.696204-07:00 WARNING mosys[2816]: libminijail[2816]: allowing syscall: socket
2018-08-01T11:07:57.696218-07:00 WARNING mosys[2816]: libminijail[2816]: allowing syscall: connect
2018-08-01T11:07:57.696225-07:00 WARNING mosys[2816]: libminijail[2816]: allowing syscall: sendto
2018-08-01T11:07:57.696230-07:00 WARNING mosys[2816]: libminijail[2816]: allowing syscall: writev
2018-08-01T11:07:57.701091-07:00 WARNING mosys[2816]: libminijail[2816]: logging seccomp filter failures
2018-08-01T11:07:58.489396-07:00 INFO crash_reporter[2828]: libminijail[2828]: mount /dev/log -> /dev/log type ''
2018-08-01T11:07:58.500685-07:00 WARNING crash_reporter[2828]: [user] Received crash notification for flashrom[2820] sig 31, user 0 (developer build - not testing - always dumping)
2018-08-01T11:07:58.501804-07:00 INFO crash_reporter[2828]: State of crashed process [2820]: S (sleeping)
2018-08-01T11:07:58.503603-07:00 INFO metrics_daemon[2109]: [INFO:metrics_daemon.cc(427)] Got org.chromium.CrashReporter.UserCrash D-Bus signal
2018-08-01T11:07:58.508030-07:00 INFO crash_reporter[2828]: Stored minidump to /var/spool/crash/flashrom.20180801.110758.2820.dmp
2018-08-01T11:07:58.508275-07:00 INFO crash_reporter[2828]: Leaving core file at /var/spool/crash/flashrom.20180801.110758.2820.core due to developer image
2018-08-01T11:07:58.508577-07:00 WARNING crash_reporter[2828]: [ARC] Received crash notification for flashrom[2820] sig 31, user 0 (ignoring - crash origin is not ARC)

2) mosys eeprom map also leads to
# mosys eeprom map 
Child process did not exit normally.

/var/log/messages and crashdumps are attached
messages
769 KB View Download
flashrom.20180801.111320.2893.meta
153 bytes Download
flashrom.20180801.111320.2893.dmp
26.7 KB Download
flashrom.20180801.111320.2893.core
724 KB Download
flashrom.20180801.110758.2820.meta
153 bytes Download
flashrom.20180801.110758.2820.dmp
26.8 KB Download
flashrom.20180801.110758.2820.core
724 KB Download

Comment 1 by apronin@chromium.org, Aug 1 

mosys also crashes on boot. Debug logs & contents of /var/spool/crash are attached.
debug-logs_20180801-111929.tgz
639 KB Download
var_spool_crash.tgz
255 KB Download

Comment 2 by apronin@chromium.org, Aug 1 

Sounds like http://b/112037192, but in x86 (fizz) case.

Comment 3 by apronin@chromium.org, Aug 1

Cc: jclinton@chromium.org xzhou@chromium.org
Owner: samanthamiller@chromium.org
Hi Samatha, could you please also take a look at seccomp issues for mosys/flashrom on other platforms. Here seems to be an example for x86. I see https://crrev.com/c/1158981, but it fixes it for arm only.

Wasn't able to find a general bug open for it, but maybe I just missed and it's a dup already.

Comment 4 by apronin@chromium.org, Aug 1

Labels: M-70 OS-Chrome

Comment 5 by samanthamiller@chromium.org, Aug 1 

I now have https://crrev.com/c/1159333 that should fix the issue for fizz.
Project Member

Comment 6 by bugdroid1@chromium.org, Aug 2 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/mosys/+/652446c789f0472e5b6ce77993401c3733de4aa6

commit 652446c789f0472e5b6ce77993401c3733de4aa6
Author: Samantha Miller <samanthamiller@google.com>
Date: Thu Aug 02 20:52:57 2018

mosys: Fix fizz mosys seccomp issue

BUG= chromium:869971 
TEST=built and ran failing commands on fizz machine

Change-Id: I38767b7298d1cc39fdba41517bca97dfeaa3f46a
Reviewed-on: https://chromium-review.googlesource.com/1159333
Commit-Ready: Samantha Miller <samanthamiller@google.com>
Tested-by: Samantha Miller <samanthamiller@google.com>
Reviewed-by: Jason Clinton <jclinton@chromium.org>

[modify] https://crrev.com/652446c789f0472e5b6ce77993401c3733de4aa6/seccomp/mosys-seccomp-amd64.policy

Comment 7 by samanthamiller@chromium.org, Aug 3

Status: Fixed (was: Untriaged)
Let me know if this still isn't fixed.
►

Sign in to add a comment