usbguard: madvise missing from seccomp policy |
|||
Issue descriptionA crash was reported in usbguard related to a missed syscall in the seccomp policy: https://buganizer.corp.google.com/issues/117116656
,
Oct 22
Issue 897569 has been merged into this issue.
,
Oct 22
,
Oct 29
Curious, why was this reported as fixed? I see the following crash tagged to this bug: https://crash.corp.google.com/browse?q=product_name%3D%27Chrome_ChromeOS%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27__libc_start_main%27+AND+product.Version%3D%2771.0.3578.21%27&stbtiq=&reportid=&index=0
,
Oct 29
kkaluri mistakenly marked 897569 as a duplicate of this issue. I have cleared that marking.
,
Nov 21
Issue 907169 has been merged into this issue.
,
Dec 17
Issue 915350 has been merged into this issue.
,
Dec 17
We might want to merge back to m-70 since this is a simple 1 line seccomp policy change and would take care of those crash reports. There isn't any functionality that is impacted by these crashes though because the feature is disabled. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Oct 2