mosys: do not log seccomp failures |
||||||
Issue descriptionlogging seccomp failures is useful for debugging, but it shouldn't be used on production devices. it spams log files and whitelists a number of syscalls that we normally don't want.
,
Aug 27
Why is this blocking M70? This is just 'too much logging' right? (Not an accusation, I actually don't understand).
,
Sep 4
Friendly ping to get an update as it is marked as RBB. Thanks
,
Sep 4
Since samanthamiller@'s internship is over I think this needs more context for someone else to pick it up. Is the request here only to disable this logging for production images?
,
Sep 4
it should be disabled all the time looks like this was just cleaned up in issue 872187, but we're having to roll back due to failures it tripped up i added M-70/beta blockers to make sure this actually got addressed in time. this is new code to M-70 and we shouldn't be shipping it in this debug mode.
,
Sep 11
Friendly ping. Checking on the progress of these RBBs, please update with an ETA on fixes if this issue is still an RBB. Otherwise please remove the RBB label. Thanks.
,
Sep 12
This is blocked on issue 872187.
,
Sep 19
Fix merged to master and R70 in blocking bug.
,
Sep 19
[Auto-generated comment by a script] We noticed that this issue is targeted for M-70; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-70 label, otherwise remove Merge-TBD label. Thanks.
,
Sep 19
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by vapier@chromium.org
, Aug 21